Skip to content

Email setup & migration

Everyone on your team writing from your own domain, with the old mail moved in

Discuss a Project

The problem

Your team writes from personal Gmail addresses or an old hosting mailbox that keeps filling up, and some of your messages end up in spam.

It’s awkward to send a quote from a personal address and then wonder whether it reached the client.

Your email should look like your business and reach the people you write to.

Who it's for

Small businesses setting up email on their own domain for the first time, and teams moving from one email provider to another.

If nothing changesClients notice a personal address. And without the sending records, your quotes and invoices are more likely to land in spam.

The scope

Included

Google Workspace or Microsoft 365 set up on your domain Mailboxes, aliases and shared inboxes Old mail, contacts and calendars moved SPF, DKIM and DMARC records Setup notes for phones and mail apps

Not included

Licence fees (you pay Google or Microsoft directly) A promise that no message ever lands in spam Newsletters and bulk sending

What we need from you

Access to your domain’s DNS settings Sign-in to the old mailboxes, or an admin who has it A list of who needs which address
Three steps, in writing

How it works

01 Tell us what’s not workingA few lines is enough. A person reads it and replies by email.
02 Approve a written scopeIncluded, not included, inputs, measures and estimate. Nothing starts until you sign off.
03 See what changedWe work in agreed checkpoints, then check the result with you against the agreed measures.
What you can count on
You own it allAccounts, content and code are registered to you.
Nothing starts without your sign-offYou approve a written scope and estimate first.
No surprise workAny change to the scope is agreed in writing.
No promises we can’t keepWe agree what to measure and show you what moved.
Does this match your situation? Start with step 1: tell us what's not working. Discuss a Project
After it's doneA mailbox on your domain for everyone who needs one, the old mail in place, and SPF, DKIM and DMARC set and checked.

How we measure

We agree what to track before work starts. Get the Written Scope Checklist →
01A test message sent and received for every mailbox
02SPF, DKIM and DMARC checked after the switch
03Message counts compared, old mailbox against new

Questions

  • We copy the old mail before the switch and compare message counts afterwards. Keep the old account until you’ve checked that everything is there.

  • It depends on the tools your team already uses: Microsoft 365 if you work in Word and Excel, Google Workspace if you work in Gmail and Google Docs. We help you choose before setup starts.

  • Mail keeps arriving, but while the DNS change spreads, some of it can still land in the old mailbox. We plan the switch for a quiet time and copy anything that arrives there late.

  • It depends on scope. You get a timeline in the written plan before any work starts.

  • It depends on the number of mailboxes, how much old mail there is to move and where it is now. You get an estimate for the agreed scope, in writing, before any work starts.

  • You do. Accounts, content and deliverables are registered to you.

Other services