1. What are the source and destination?
List systems, account types and connection methods. Confirm access permissions and service limits; different endpoints may require different methods.
2. Which data must move?
Inventory email, calendars and contacts separately. Record account counts, data volume and scope, then verify support for each data type in the actual environment.
3. When will cutover happen?
Agree acceptable disruption, user communications and owners. Include account preparation, operational steps and validation responsibilities in the cutover plan.
4. How will the pilot work?
Use representative accounts and data to test connectivity, transfer and destination usability. Document limitations before scaling up.
5. How will completion be verified?
Define checks, discrepancy handling, retries and user confirmation in advance. A completed progress indicator alone is not project acceptance.
