Email migration

Move your business email with a clear plan.

Changing email providers should come with a plan for your data, your users and the changeover. I scope the move, carry out the migration and check the result against your source before handing it back.

Work directly with Edwin, from scope to handover.

The approach

Know what happens next.

  • A migration plan

    I review the source and destination, mailbox sizes and access, then agree the scope and a realistic schedule with you.

  • A clear account of what can move

    Email, folders, labels, contacts and calendars are assessed against the capabilities of both platforms. Any limitations are explained before the move.

  • An agreed changeover

    I plan background copying and the MX or DNS change with you, including how your team will access email during the transition.

  • Source and destination checks

    I compare the migrated mailboxes with the source, review exceptions and test sending and receiving. The source data is retained during verification.

  • A documented handover

    You receive a report of the work and checks, plus user guidance. Training and the support period after migration are confirmed in the scope.

What helps me scope your project

You do not need every answer before getting in touch. Share what you know, and we can work through the rest together.

  • Which platforms and accounts are you moving from and to?
  • How many mailboxes are involved, and how much data do they hold?
  • Do contacts, calendars, shared addresses or delegated access need to be considered?
  • Who controls the domain, DNS and administrator accounts?
  • Is there a preferred changeover date or a period your team needs to avoid?

Project example

A large Drive and email migration.

What a full account move looks like when the data is measured and the exceptions are recorded.

A business owner needed their existing Drive files and email moved into a new Google Workspace account. I migrated 1.22 TB of Drive data, preserving the folder structure and keeping the original account data in place.

The email migration imported 37,186 of 37,257 discovered messages. The remaining 71 messages did not import and were recorded in the delivery report. I also completed domain authentication in Constant Contact for the client’s marketing email setup.

The handover explained the migration results and the need to recreate Drive sharing permissions in the new account. The client was directed to make future edits in the destination account while retaining the original data for review.

1.22 TBof Drive data moved
37,186of 37,257 emails imported
71emails recorded as exceptions

The delivery report recorded that 71 messages did not import and that Drive sharing permissions needed to be recreated in the new account.

Questions about this service

Details before decisions.

The final scope is always confirmed for your specific setup.

Can you move between Google Workspace and Microsoft 365?

Yes. I also work with Zoho, GoDaddy and webmail hosts. I first check the particular source and destination to confirm what can be transferred and how it will appear in the new account.

Will my email keep working during the move?

I plan the copying and changeover to reduce disruption. What your team needs to do, and any limitations around access or delivery during the change, are explained in the migration plan.

Does the mailbox price include licences and subscriptions?

Your written quote identifies the service scope and any required migration software or subscriptions. Provider billing stays on your own accounts, and you approve the costs before work starts.

Related help

Another part of the picture?

Let’s start with your situation

What does your email
need to do better?

Describe the problem or the move you are planning. I’ll help you work out the next step and confirm the scope before any paid work.

Tell me what you need Book a free intro15 minutes · A conversation about scope

Original Fiverr review