Account migration refers to the transfer of accounts and account information between workspace environments. Account migration copies inbound and outbound messages as well as account-level reporting data to a selected destination workspace environment. This article shares more details about the account migration process.

Areas impacted during migration

Specifically, only the following will be migrated:

1. Outbound - Scheduled, Approval, and Sent Messages will be copied over to the destination workspace.

2. Inbound - All messages will be available in the destination workspace.

3. Reporting - All Account level and Post level reporting data will be visible in the destination workspace.

​

The following will not be copied:

1. Outbound - Draft messages will not be copied to the new workspace.

​

Known issues and limitations:

1. Posts that are published or scheduled to be published during the migration may fail.

2. Approval messages which are in the middle of a tiered approval will still continue on the same approval path, even though that same tiered approval will not exist in the destination workspace. If the message is rejected and sent for approval again, only the tiered approvals in the destination workspace will be available.

​

The migration does not move all configurations and other assets. You may have to recreate or share these with the destination workspace. This list is not exhaustive and only includes some of the most commonly related settings around accounts.

​

For Example:

1. Users Settings: Users that previously had permissions in the source client may not exist in the destination client. The users will need to be added to the destination client.

2. Account Sharing: If you want publishing to be available in the source client after the migration, please share the account with the source client.

3. Engagement/Reporting Dashboards: Dashboards will need to be recreated or shared with the destination client.

4. Social Apps: Templates are not copied over. If a page is migrated, you will be unable to reinstall or take a snapshot until the template exists in the destination client.

5. Rule Engine: Client Level rules with account message source conditions will need to be recreated in the destination client.

​

Note: To prevent any issues during the migration process, the Product Support team will work with your Success Manager to schedule account migration.