Hi @RashidJorvee ,
This is a loaded question but there are some things to consider:
- Any logic in your tag manager which is dependent on URL/Domain
- Any processing rules dependent on URL/Domain
- Any segments using URLs or Domains
- Cookies which are set against the domain name
- ....you get the idea. If you're using a domain (full or partial) or URL in your logic across your implementation, you'll need to revisit these
- First party collection name for analytics sever (ie: metrics.abc.com -> metrics.xyz.com
- Settings in your library configurations which point to analytics or use analytics domains/URLs
- Any certificates for the impacted/new domains
I would say that a complete and thorough audit is required of your implementations to assess the potential impact. It's a bit of an intensive process but critical for risk mitigation. Your report suite doesn't go anywhere provided you keep it intact, but you would need to update your analytics implementation to be certain that you're addressing all data points impacted.
You may want to run a parallel container/RSID to test pre- and post-migration (compare a set of the same pages on different domains assuming all other factors are unchanged).