Check the dependencies before moving the mailboxes.
Planning checklist for a scope conversation—not environment-specific instructions or a guarantee that a migration is ready.
Start the Assessment · Call (219) 256-5454
Establish the starting condition.
Record the source environment, tenant, domains, platform versions, mailboxes, shared resources, data volumes and known failures. Confirm the administrator and application owners who can answer questions and approve changes.
Review identity and access.
Understand directory health, synchronization, user sign-in, administrative roles, shared access and service-account dependencies. Changes to authentication need their own validation scenarios.
Map mail flow and applications.
Identify inbound and outbound routing, relays, scanners, copiers, application notifications, third-party filtering, connectors and certificates. Verify which systems remain after mailbox migration.
Clarify information requirements.
Review the required retention, legal hold, archive, backup, sharing and access expectations with the responsible organizational owners. Product settings alone do not define those obligations.
Design representative tests.
Choose users and scenarios that cover ordinary mail, shared resources, external delivery, mobile or desktop clients and dependent applications. Include the planned failure and rollback decision points.
Plan cutover and handoff.
Identify maintenance windows, communication, support ownership, validation records, remaining infrastructure and stabilization. Retire legacy services only after their actual dependencies have been addressed.
Use the findings to scope the work.
A missing answer may create a discovery or remediation task. Bring a high-level summary to Ask Buc; do not upload credentials or confidential exports to the public form.