Hoping for some thoughts / advice on the approach for this. I'm in the middle of an upgrade / migration project from an SP2010 to SP2016 environment. Due to gaps in versions, the approach we take is to provision an SP2016 environment, create the required topology, and then use a migration tool (most likely Sharegate) to actually migrate the content from the ; old environment to new environment.
Existing usage is fairly straightforward (there is not a lot of customization) but the volume data is not trivial – it is at least a few hundred GB, currently all in one database content data. For this reason, in the context of migration, it makes sense to reorganize a bit and ensure, for example, that site collections have their own database.
Anyway, the question / advice: there is a sub site from the root site collection which has a lot of content and this is the one I would like to move to its own site collection so that its data can go into a separate content database. The problem is that the URLs will have to stay the same after the migration because they are linked to another system.
I will try to illustrate! Currently, there is a SP2010 server, which we will call SP2010SERVER. There is a CNAME in DNS that points to (with AAM configured AFAIK), for example, SHAREPOINT. So, for now, you can browse the content in SP2010SERVER using the DNS name of SHAREPOINT. There is a subsite, which we will call SUBSITE1, and the URLs are there for example, http: // sharepoint / subsite1. (Note: there are many other subsites and site collections with managed paths, etc.)
We have the new SP2016 server; which let's say is called SP2016SERVER. Once done, the idea is to switch the DNS record so that SHAREPOINT is now pointing to SP2016SERVER.
I need to move the current SUBSITE1 to its own site collection in the new environment while keeping the URL of http: // sharepoint / subsite1. Migrating content to the root site of a new site collection is pretty trivial, I think, but the question is how to keep the URL. I cannot use a managed path (afaik) because if I configured for example, “ subsite1 & # 39; & # 39; as a managed path, it would still need a site collection name after the path.
I have studied host-name (d) site collections as a possible solution. I think in this case you can more or less specify any URL for the site collection, but I haven't used them before and all of the examples I've seen tend to use a sort of subdomain.domain.tld. type configuration.
Would it work for my needs? If not, are there any other solutions or options for this?
I imagine I could get the same thing with some sort of IIS magic / redirect, etc., but I was hoping to avoid that if possible.
Thanks for any thought / help!