Please find below the detailed steps involved in the migration of Viva Engage(Yammer) data from one Data Centre to another (e.g: US to EU).
| Step # | Action | How it happens ? |
|---|---|---|
| 1 | Perform a Backup Sync from your Source Data Center | Through Yammer Export in the Apps4.Pro Migration Manager tool |
| 2 | Reprovision of Source Data Center | Reach Microsoft for Reprovisioning |
| 3 | Intimate users not to use Viva Engage(Yammer) | IT admins to inform the users via mail / chat or other collaborative methods |
| 4 | Perform an Incremental Sync before 4 to 5 days of the Reprovision cut-off | Re-run the Yammer Export Job created in Step #1 |
| 5 | Completion of reprovisioning | Microsoft completes the reprovisioning |
| 6 | Individual users have to login to their Target Viva Engage(Yammer) to ensure ‘User Impersonation’ Note : Skipping this step will result the messages being posted by the Service Account instead of the user. |
Users to login to their Target Viva Engage(Yammer) |
| 7 | Intimate users not to use Viva Engage(Yammer) until further notice to avoid mix-up of migrated posts with the current posts | IT admins to inform the users via mail / chat or other collaborative methods |
| 8 | Block email notifications to end users during migration | Create an Exchange Transport Rule to achieve the same |
| 9 | Import the backed-up data to the Target Data Center | Through Yammer Import in the Apps4.Pro Migration Manager tool |
| 10 | Intimate users to start using Viva Engage(Yammer) upon completion of Import | IT admins to inform the users via mail / chat or other collaborative methods |
