Ryan Ormrod
Remote · UK hours

Home · Services · Email migration

Email migration

Ryan Ormrod · independent developer

Move mailboxes without losing a week of mail

Mailbox copy, alias mapping and MX cutover in the right order, with devices updated after the switch, not before.

Tell me how many mailboxes and where you are going. I plan the sequence so mail keeps landing.

chips mailbox copy aliases mx cutover

Email moves

Mail keeps arriving while you change provider.

Mailbox copy

History across without a blank inbox day.

Aliases and groups

Mapped before MX moves.

MX cutover

Timed, with a watch window.

Device guidance

What staff change and when.

If that matches the job, send the brief.

Process

Copy, map, cut over

Same delivery shape on every service page. The labels change with this job.

  1. 01 Done

    Inventory

    Users, aliases and DNS.

  2. 02 Now

    Copy

    While old MX still receives.

  3. 03 Next

    Cut over

    MX change in an agreed window.

  4. 04 Next

    Settle

    Devices and any stragglers.

Who

Who this is for

Businesses changing host or Google/Microsoft tenancy.

smb

Small business owner

Mailboxes that must keep working through a host or provider change. Planned cutover, MX timing and mailbox checks.

See matching services
large

Large business owner

More stakeholders, staging discipline and handover that still makes sense across teams.

See matching services
agency

Agency

Client email move under your brand. Quiet delivery with a checklist your client can follow on the day.

See matching services
other

Other

Anyone who cannot lose mail for a week. We migrate carefully and confirm send and receive before calling it done.

See matching services

Rates

£30 an hour. No retainer.

Pay for the hours the job needs. Nothing sitting on a retainer.

RATE£30/hourQuoted from the hours the job needs
MODELNo retainerNo unused support contract
START50% depositWork begins when it clears
STOPUnused hours backIf you withdraw from the deposit
AGENCYWhite-label / NDAYour client stays yours

Same commercial terms on every service page and the homepage. Estimate first, then deposit.

What happens next

After you send the brief

Same sequence on every service page. No surprise retainers.

  1. I reply

    Hours or a fixed figure, plus the access I will need to start.

  2. You decide

    Deposit clears, then work begins on staging. Nothing public until you approve.

  3. Handover

    Working change, notes your team can own, white-label if you asked for it.

Same path on every service page. Send the brief when you are ready.

Send the email migration brief

07 · Send me a job

Brief, Figma, ticket or repository

Studio name, the work, the stack, a Figma or Git URL, and the staging hostname you will point at my server. Include a digital NDA link. I quote that job and stay off your client’s inbox.

  • OperatorRyan Ormrod
  • ModelRemote · no retainer
  • ScopeCode · your client stays yours
  • StagingYour hostname, pointed at my server
  • After payYou deploy the code, or I do
ryanormrod / brief in / staging out

This brief comes to me. A quote for your slice follows by email or WhatsApp. Include the digital NDA link with it. Do not send passwords here. I do not take phone calls.

Send the email migration brief