Request an Architecture Briefing

Defined implementation

Migrate email to Microsoft 365, with every mailbox checked.

Email is moved on the agreed date, mail is arriving and sending on the new path, and every mailbox is checked against the original list.

Plan the Email Move Review scope & terms

Price fixed after a short scope call. Price drivers and project calendar ↓

Illustrative sample · constructed example

A mailbox can move while its mail flow is still unresolved.

Pilot wave · accounts mailbox

Source mailbox

Mail, calendar and delegated access in the agreed inventory.

Mail-flow dependency

The accounts application still sends through the old relay.

Microsoft 365

Pilot mailbox and shared access checked before the next wave.

Selected check

Can the accounts application send through the agreed replacement route?

Evidence
Mailbox comparison complete; application send test missing.
Decision
Hold this wave
Next action
Application owner supplies the sending configuration and a test window.

Illustrative sample. Each agreed mailbox is checked; unresolved differences stay in the acceptance record.

Related validation method: this delivered record concerns SharePoint files. It is not evidence of this email migration.

Inspect the related record ↗

Open the complete illustrative document to inspect its fields and print a copy.

Open the sample document ↗

Email Migration

The work starts here.

Email has to move off an old host, an old server, or another company’s system, and there is a date it has to be done by.

Scope considerations

  • One coordinated owner for the switch
  • Checked mailbox by mailbox before sign-off
  • You own staff support on the day

What AZ changes or delivers

  1. 01

    Every mailbox in scope is counted before anything moves, and each one gets a named destination.

  2. 02

    The things the old system quietly owns are mapped, including the records that tell the internet where to deliver your mail.

  3. 03

    The conditions that stop the move are agreed in writing beforehand, naming what would trigger a stop rather than promising to be careful.

  4. 04

    The move runs on a dated schedule in groups, and each group is checked before the next one starts.

  5. 05

    The new system is checked mailbox by mailbox against the old one, and every gap is closed or given an owner.

Acceptance

Checks before handover

  • Every mailbox on the agreed list has arrived at its destination

  • Sending and receiving are tested on the new path

  • Every mailbox is counted back against the list you started from, and anything missing is either recovered or handed over with a named owner

Scope, price and project calendar

Engagement price

Price fixed after a short scope call.

The price is agreed in writing before any work starts and before anyone is given access. The call itself costs nothing. What moves the number:

What determines the scope

  • How many mailboxes are moving
  • What system the mail is coming from, and whether both systems have to work side by side during the move
  • Whether archives, shared mailboxes, public folders or legal holds are included
  • Whether the switch has to run outside business hours

Delivery calendar

The calendar is set once the data, the dependencies and the cutover requirements have been checked, then fixed in writing before the move begins.

How engagements work

Scope & responsibilities

Responsibilities and exclusions

Review the exclusions, required client participation, change controls and operational handover for this engagement.

Exclusions
  • Licenses needed to run the move
  • Fixing faults in the old system before the move
  • Cleaning up mail before it moves
  • Help desk and staff support
Client responsibilities
  • Approve the date and time of the switch
  • Tell your staff what is happening and support them on the day
  • Give administrator access to the old and the new system
Change and rollback method
  • Mailboxes move in dated groups, and a group is not started until the one before it checks out.
  • The conditions that stop the move are agreed before the first mailbox moves, and they name conditions rather than intentions.
  • The records that route your mail are changed with their timers shortened in advance, so undoing it takes minutes instead of a day.
Operational record and handover
  • The counted list of every mailbox that moved
  • The dated schedule, as it actually ran
  • The map of what the old system quietly owned
  • The agreed conditions for stopping
  • The check sheet proving old and new match

Access, acceptance and support arrangements ↗

Discuss this engagement

Discuss Email Migration

Describe the problem, systems and deadline. We will review the fit and the scope questions before preparing a written proposal.

Plan the Email Move