Preserve file path and prevent 404 issues after migrating to Netlify

[yasir]

I am building a site on Next.js and migrating the content on Headless CMS from WordPress. I have 4 GB of assets (Images, Videos, PDFs, etc) on WordPress which means after moving to Headless CMS, I am having thousands of 404.

I do not want to use those images now onwards BUT the thing is that they are indexed in Google and after migrating we will have thousands of 404. To avoid 404 issues, I need to keep those assets (Images, Videos, PDFs, etc) somewhere with maintaining their current URLs. Like
http://www.example.com/wp-content/uploads/2019/07/image.jpg

We need to keep this URL and avoid 404. This is just an example. We are looking for a way in which we can add this (/wp-content/uploads/) folder on Netlify and remains there without having an effect on our build time. This is just a static folder which will be used to avoid 404 issues.

Is that possible with Netlify? If yes, then HOW if not then do you guys can suggest some alternatives?

Thanks in advance.

[perry]

Hmm, I think your research should start here:

https://docs.netlify.com/routing/redirects/

Give this a read through and let us know what you think.

[yasir]

I think you don’t understand my request, We are looking for a way in which we can add this folder on root (Netlify) and remains there without having an effect on our build time. This is just a static folder which will be used to avoid 404 issues. even these url would no more used in our codebase. and this folder remains unchanged for future. like:
https://example.com/folder/

so assets which was indexed with the old url keep live.

[gregraven]

I could be mistaken because I don’t use that static site generator, but if you add them to your project and upload them as static assets, there should be no impact on your build time other than the first time they are transferred to Netlify.

Of course, this is assuming your build process includes GitHub or GitLab. If you are ZIPping up your site folder and uploading that manually, this amount of content could cause issues.

[perry]

ah, OK.

is there anything helpful in here?

[Common Issue] Making the most of Netlify's CDN cache

Our CDN derives much of its efficiency from files whose checksums don’t change between deploys. For instance, in a blog, you usually write or update one article in one file, while the rest of the content remains unchanged. In this typical use case, we don’t need to re-upload and re-process these files, since our CDN already has them stored - no checksums have changed except the one file. This also means that your visitors’ browsers don’t need to re-download any files, since they already have …

https://answers.netlify.com/t/common-issue-how-does-netlify-s-cdn-handle-caching-files/103/5