I'm migrating a medium-sized site (12,000 pieces of content) from Static HTML to a CMS. The CMS effectively requires that the exiting site structure has to change. The site has more than 5,000 PDFs with internal links that include the FQDN, along with hundreds external links.
These PDFs will not be updated as part of the migration, or at a later date, so I will need to create redirects for each piece of content on the old site to its counterpart on the new site, and maintain those redirects effectively forever.
The existing site and links are at
http://www.example.com. I would very much like to use wildcard redirects where possible (like in the directory structure that contains 2,000 MP3 files).
Unfortunately, I probably can't just use the
http://example.comroot domain for the new site, leaving www for the old one, because it conflicts with their internal Active Directory. (When an internal user goes to
http://example.com, it takes them to an internal Active Directory domain controller.) So www is fine, but using the root domain isn't.
The next easiest way to do this is with a new domain name, leaving the old domain to redirect content forever. This would work, but is the least desirable outcome for the business.
My other thought was to use something like
www1.example.com, but I'm not sure if there are SEO implications or other issues using
www1as canonical. Most sites that I've seen use www1 use it as an alternative to
www, not a replacement.
I could try putting redirects on the same server and domain name as the CMS (retaining
www.example.com), but that seems like it would be problematic. I would have 12,000 redirects, and if the business ever created a live content item with the same path as a redirect, one of them wouldn't work.
It's not terribly desirable (and maybe not possible) to put everything on the new site under
www.example.com/newsite/to avoid redirect conflicts.
Anything I'm missing, or other advice on how to approach this?