The data was successfully moved to the new location. Thank you/project close out: Let them know that the project is complete.However, if you migrated email archives to Office 365, you might want to use this opportunity to give them some Office 365 training resources. Training information: If your project was a tenant-to-tenant migration, users probably won‘t need any training information.If resting doesn’t keep you too busy, you can reach out to users again with these messages: Again, encourage them to contact you if they notice anything abnormal.Īll data is moved to the new location-yay! This is when you finally start sleeping again and plan your next vacation. Welcome: Tell the user that their data was successfully moved.Encourage them to contact you if they notice anything out of the ordinary. Moving day: Let the users know when their data is next to move to the new system.Here’s what you might want to tell users during this step: Users will probably move to the new system in waves (or batches). It’s go time! Your tests are done and you’re ready to start moving data to the target system.
There’s not really anything to communicate with users during this phase unless you want to send more of those reminder emails I mentioned at the end of the Planning section above. You’ll test the setup with just a few users. Reminder: For those who are prone to miss (not read) email messages, you might decide to send an email (or a few emails) reminding users about the items from the project announcement and downsizing emails.ĭuring this phase, you’ll set up the source and target environments.Education: You might send information teaching users about the new systems and features you’re implementing.You might also have them clean up old permissions. Downsizing: You might ask users to clean up files and folders they manage, so you’re not moving unnecessary or duplicate data to the new environment.Project announcement: You might send an email explaining the integration/migration project to users and giving them an idea when the project will take place.During this phase, you might decide to communicate to users: You determine when to start the project and when you hope it’s complete. This is when you’ve decided to move the data and you begin getting everything ready for the project. Let’s take a closer look at the process: Phase 1: Planning Phases of Office 365 migrationīefore you decide when (and what) to tell users about the migration, you need to understand the phases of the project. Then, you’ll get some communication templates you can copy, edit, and send to users to tell them about your upcoming project. First, you’ll see an overview of the phases of a migration project. If you’re looking for some email templates to send to users, look no further. Either way, you might wonder what to tell the users whose data is getting migrated. Or, a merger, acquisition, divestiture, or consolidation might mean you‘re moving things around in the cloud-an Office 365 tenant-to-tenant migration. You’re about to move your data-congratulations! You might be moving from a legacy system into Office 365.
0 kommentar(er)
