What is the process of migration of report suites to a different login company? What other considerations need to be taken when migrating to a new company?
Note that the information provided in this document is specific to Adobe Analytics (except for the part related to user migration). This document does not cover impact/process for other Experience Cloud solutions.
The process of company migration is partly supported by customer care. While some of the steps are covered by Customer Care, others need to be completed by Adobe provisioning team. It is recommended to work with your account manager to help you with the steps and the provisioning required. This document lists and explains the changes that need to be considered while planning the migration.
There is no physical migration of report suites from one company to another. It is just linking the report suites to the new company and removing the linkage from the old company. As a result, report suites will start showing in the new company and will be hidden from the old one.
Report Suites are migrated in two steps
Report Suite Mapping
Report Suites need to be mapped to the new Experience Cloud Org. You would need to contact support to map the report suites to the new Experience Cloud Org.
Since data resides in report suites, data is also migrated with the report suites. No data loss is expected in the process.
Login company assets are different than report suites and they belong only to the login company where they were created. As of now, there is no automated way to migrate assets from one company to another, except recreating them manually. Below is the list of assets to consider:
Product Profiles/User Groups
Users cannot be transferred from one company to another. They need to be re-created in the new company.
Users cannot be transferred from one company to another. They need to be re-created in the new company. The recommended way is to export the users from the old company in CSV from Admin Console and import them (after making necessary changes in the CSV) via the Admin Console of the new company. Here are the steps:
There is no impact of migrating report suites, assets and users on data collection. However, due to contractual agreement, the new company should use a separate DTM/Launch property to host tags as well as a new tracking server (which is unique for each company).