Onboarding

Your first week, hour by hour

“Live in under a week” is a claim, so here is the working. Four phases, what we do in each, what we need from you, and what exists at the end that did not exist before.

1Day 1

The setup call

Twenty minutes. You tell us the workflow that eats your week; we tell you the plan, the price, and the go-live date.

What we do

Ask what actually takes the time — the inbox, the filing, the chasing — and which one we should remove first.
Look at where your mail and files live today, so we know whether this is a migration or a fresh tenant.
Confirm the plan that fits your headcount, what we cost including any seat overage, and what Microsoft will charge you for licences on top.
Agree exactly which mailboxes and sites we will need, then have your admin consent to our named application (the permission set is fixed and tenant-wide).
Put a go-live date in the calendar, and tell you which day mail moves.

What we need from you

Bring whoever can answer questions about your domain and your current email.
Tell us honestly what has been tried before and what broke.

At the end of this phase

A written scope: the plan, the first automations, the cutover date, and the access we will hold.

Days 2–3Phase 2 of 4

Tenant and mail cutover

We stand up your Microsoft 365 tenant, verify your domain, move mail across, and configure OneDrive and your SharePoint team site.

What we do

Stand up or take over your Microsoft 365 tenant and verify your domain.
Publish the mail records — MX, SPF, DKIM, DMARC — so mail routes correctly and is not treated as spam.
Migrate mailboxes, calendars, and contacts from wherever they live now, with a sync running before we switch anything.
Configure OneDrive with Known Folder Move, and build the SharePoint library and permission structure we agreed.
Set up each person's desktop and mobile profile so nobody has to configure their own phone.

What we need from you

Give us access to your DNS, or be available to make one record change while we are on a call.
Give us a list of mailboxes, shared addresses, and distribution groups that must exist on day one.
Tell your team the date — the only thing they will notice is being asked to sign in again.

At the end of this phase

Mail, files, and team sites live on your own tenant, with the old system still reachable while DNS settles.

Days 4–7Phase 3 of 4

Automations live

Your included automations go in one at a time, each one tested against real mail before we hand it over.

What we do

Build each automation on Azure, running through the one Microsoft Graph application your admin consented to.
Test it against a batch of your real mail and documents before it touches anything live.
Wire the audit logging for your account, so every action an automation takes is recorded.
Walk the owner of each workflow through what it does and where to look when it has run.
Set up ID360 AI in your tone, and agree what it may draft versus what a person must always write.

What we need from you

Nominate an owner for each workflow — the person the routing should reach.
Give us a handful of real examples: a typical invoice, a typical enquiry, a reply you were happy with.
Review the first week of output and tell us what is wrong. It usually needs one round of tuning.

At the end of this phase

Your included automations running on live mail, each with a named owner and a visible record of what it did.

OngoingPhase 4 of 4

We run it

We keep your automations running, make seat changes on request, and refine the ID360 AI assistant around how your team works. Monthly or annual — cancel anytime, and your plan runs to the end of the period you paid for.

What we do

Monitor the workflows and fix them when they break, usually before you notice.
Add and remove users as people join and leave, and reclaim the licences.
Adjust filing rules, routing, and drafting as your vendors, clients, and team change.
Review what is running with you when you ask for it — Scale includes a scheduled quarterly review.

What we need from you

Tell us when someone joins or leaves.
Tell us when something starts feeling like busywork again — that is the next automation.

At the end of this phase

A Microsoft 365 that someone is actually looking after, on an arrangement you can end whenever you choose.

The one everybody asks

You will not lose mail. You may briefly receive it in two places.

We keep the old system accepting mail while the new one comes up, so nothing bounces. Once we change your MX record, the internet takes time to notice — typically under an hour for most senders, but up to 24–48 hours for the slowest, because that is how DNS caching works and no provider can shorten it. During that window some mail arrives at the old system and some at the new one; we keep both running and reconcile at the end. The switch itself is scheduled with you, usually outside business hours.

The full migration paths

The whole checklist, before you start

Everything we will ask you for, in one place. Having these ready is the difference between a week and a fortnight.

Access to your domain's DNS

Mail routing, and proving the domain is yours. Either give us access or be on a call while you make the changes yourself — both are fine.

A list of mailboxes and shared addresses

Every person, plus the addresses a team answers together — sales@, invoices@, info@. Missing one is the usual cause of a bumpy first morning.

Where your mail and files live today

Google Workspace, an existing Microsoft tenant, an IMAP host, or an on-prem Exchange server. It changes the method, not the price.

An admin login for the current system

Migration reads from the old system. Without admin access we can only move mailboxes one at a time, with each person's password.

Admin consent on the new tenant

You grant it in your own admin center — the permissions are tenant-wide, and you can revoke it there at any time. We never hold a standing password to your tenant.

A few real examples

A typical invoice, a typical enquiry, a reply you were happy with. Automations tuned on real documents work on the first attempt far more often.

A week is the shape of the work on a typical small team, not a contractual commitment. A large mailbox count, an on-premises Exchange server, or a DNS provider we cannot reach will move the date — and we will say so on the call rather than after you have signed. The consented application, audit logging, and the automations themselves are all set up for your tenant during this week; none of it is switched on from a shelf.

How it works Browse automations What we manage in each app Which licence do I need?

Day 1 is a twenty-minute call

Book it and we'll come back with the plan, the price, and a go-live date you can put in the calendar.

Book a call

Onboarding

Your first week, hour by hour

“Live in under a week” is a claim, so here is the working. Four phases, what we do in each, what we need from you, and what exists at the end that did not exist before.

1Day 1

The setup call

2Days 2–3

Tenant and mail cutover

3Days 4–7

Automations live

4Ongoing

We run it

Day 1Phase 1 of 4

The setup call

Twenty minutes. You tell us the workflow that eats your week; we tell you the plan, the price, and the go-live date.

What we do

Ask what actually takes the time — the inbox, the filing, the chasing — and which one we should remove first.
Look at where your mail and files live today, so we know whether this is a migration or a fresh tenant.
Confirm the plan that fits your headcount, what we cost including any seat overage, and what Microsoft will charge you for licences on top.
Agree exactly which mailboxes and sites we will need, then have your admin consent to our named application (the permission set is fixed and tenant-wide).
Put a go-live date in the calendar, and tell you which day mail moves.

What we need from you

Bring whoever can answer questions about your domain and your current email.
Tell us honestly what has been tried before and what broke.

At the end of this phase

A written scope: the plan, the first automations, the cutover date, and the access we will hold.

Days 2–3Phase 2 of 4

Tenant and mail cutover

We stand up your Microsoft 365 tenant, verify your domain, move mail across, and configure OneDrive and your SharePoint team site.

What we do

Stand up or take over your Microsoft 365 tenant and verify your domain.
Publish the mail records — MX, SPF, DKIM, DMARC — so mail routes correctly and is not treated as spam.
Migrate mailboxes, calendars, and contacts from wherever they live now, with a sync running before we switch anything.
Configure OneDrive with Known Folder Move, and build the SharePoint library and permission structure we agreed.
Set up each person's desktop and mobile profile so nobody has to configure their own phone.

What we need from you

Give us access to your DNS, or be available to make one record change while we are on a call.
Give us a list of mailboxes, shared addresses, and distribution groups that must exist on day one.
Tell your team the date — the only thing they will notice is being asked to sign in again.

At the end of this phase

Mail, files, and team sites live on your own tenant, with the old system still reachable while DNS settles.

Days 4–7Phase 3 of 4

Automations live

Your included automations go in one at a time, each one tested against real mail before we hand it over.

What we do

Build each automation on Azure, running through the one Microsoft Graph application your admin consented to.
Test it against a batch of your real mail and documents before it touches anything live.
Wire the audit logging for your account, so every action an automation takes is recorded.
Walk the owner of each workflow through what it does and where to look when it has run.
Set up ID360 AI in your tone, and agree what it may draft versus what a person must always write.

What we need from you

Nominate an owner for each workflow — the person the routing should reach.
Give us a handful of real examples: a typical invoice, a typical enquiry, a reply you were happy with.
Review the first week of output and tell us what is wrong. It usually needs one round of tuning.

At the end of this phase

Your included automations running on live mail, each with a named owner and a visible record of what it did.

OngoingPhase 4 of 4

We run it

What we do

Monitor the workflows and fix them when they break, usually before you notice.
Add and remove users as people join and leave, and reclaim the licences.
Adjust filing rules, routing, and drafting as your vendors, clients, and team change.
Review what is running with you when you ask for it — Scale includes a scheduled quarterly review.

What we need from you

Tell us when someone joins or leaves.
Tell us when something starts feeling like busywork again — that is the next automation.

At the end of this phase

A Microsoft 365 that someone is actually looking after, on an arrangement you can end whenever you choose.

The one everybody asks

You will not lose mail. You may briefly receive it in two places.

The full migration paths

The whole checklist, before you start

Everything we will ask you for, in one place. Having these ready is the difference between a week and a fortnight.

Access to your domain's DNS

Mail routing, and proving the domain is yours. Either give us access or be on a call while you make the changes yourself — both are fine.

A list of mailboxes and shared addresses

Every person, plus the addresses a team answers together — sales@, invoices@, info@. Missing one is the usual cause of a bumpy first morning.

Where your mail and files live today

Google Workspace, an existing Microsoft tenant, an IMAP host, or an on-prem Exchange server. It changes the method, not the price.

An admin login for the current system

Migration reads from the old system. Without admin access we can only move mailboxes one at a time, with each person's password.

Admin consent on the new tenant

You grant it in your own admin center — the permissions are tenant-wide, and you can revoke it there at any time. We never hold a standing password to your tenant.

A few real examples

A typical invoice, a typical enquiry, a reply you were happy with. Automations tuned on real documents work on the first attempt far more often.

How it works Browse automations What we manage in each app Which licence do I need?

Day 1 is a twenty-minute call

Book it and we'll come back with the plan, the price, and a go-live date you can put in the calendar.

Book a call