Meetpro · Updated · 2 min read
Before you start
Inventory users, aliases, groups, shared mailboxes, calendars, files, retention requirements and applications that send email. Identify an administrator for both platforms. Keep an independent backup and do not delete the old tenant before migration and verification are complete.
Choose your Workspace plan
Match storage, meeting capacity, recording, retention and security needs to the plan. Business plans support up to 300 users. Meetpro uses Google list pricing; see the [Workspace plan comparison](/workspace) for reference rates. Licensing does not by itself include migration work.
Prepare your domain and DNS
Confirm access to your domain registrar, DNS and existing mail service. Record the current settings and plan changes to mail routing, SPF, DKIM and DMARC. Allow time for DNS changes to propagate. Only make changes as part of an approved cutover plan.
Migrate mail, calendars and files
Choose the supported migration tools for your source data. Run a small pilot, check ownership and permissions, and test calendars, recurring events and shared resources. File links, unsupported formats and application integrations may need separate work.
Cutover day
Agree the sequence, responsible people, user communications and recovery steps. Verify incoming and outgoing mail, authentication, mobile access and important workflows. Some interruption may occur; a zero-downtime migration should not be assumed.
Train your team
Provide sign-in instructions and explain Gmail, Calendar, Drive sharing and Meet. Review access and retention before retiring the source system. Training scope and migration fees belong in the written proposal. Use the [Switch to Google](/offers/switch-to-google) package to start a discovery conversation.