Perth based, with remote support across Australia. Call 0408 530 303
Microsoft 365For your business
Service overview
The service in plain English
A Microsoft 365 migration moves agreed email or file data from an existing system into Microsoft 365. The scope needs to cover accounts, devices, domain access, limitations and the checks required before changing mail routing.
From $79 an hour ex GST. The scope and fee are agreed before work begins, and enquiries get a reply the same business day.
The working scope
What we can help with
The work starts with what you need to get done. These are areas we can discuss when we scope the job.
Source system and mailbox inventory
Domain and administrator access planning
Agreed email and file migration
Changeover testing and handover
A fixed price option
Business email move to Microsoft 365
This fixed price option covers eligible small email moves. File migrations, Google Workspace moves and transfers between existing Microsoft 365 tenants are scoped separately.
One existing supported IMAP email host, one business domain and up to 3 user mailboxes, with up to 10 GB and 50,000 messages in each mailbox. These are our offer limits. The move is into a new Microsoft 365 tenant.
Start with a free scope check. Eligibility and a written quote are agreed before payment.
What the fixed price includes
One existing supported IMAP source host, one business domain and up to 3 user mailboxes, each up to our offer limits of 10 GB and 50,000 messages
A new Microsoft 365 tenant and the agreed user accounts, with two step sign in
Approved SPF, DKIM and DMARC changes, checked against the services that send your email
Copy of the email and folders in scope, with agreed mail checks
One supported desktop mail profile configured per included person
A written record of account ownership, recovery details and the agreed checks
A 30 minute handover, plus one 30 minute follow up for agreed migration issues requested within 7 calendar days of handover, with the appointment agreed with you
Check the fit
What needs a separate scope
Licences, backup subscriptions, hardware, mobile setup and onsite attendance are separate. Extra users, shared mailboxes or archives, PST files, contacts, calendars, tasks, SharePoint and other file moves need a separate scope. Moves from Google Workspace or another Microsoft 365 tenant, and incident recovery, are outside this offer.
Larger or different moves can still be discussed under the migration service above.
What we check before quoting
Before quoting, we check the source host, mailbox sizes and message counts, domain and source administrator access, and the proposed recovery and changeover arrangements. We identify website forms, scanners, marketing platforms and other services that send as your domain before approving email record changes. Oversized or unsupported items are reported and their treatment agreed before the written quote. Eligibility is confirmed before payment.
When the old email service can close
The source service stays active until the agreed final sync and checks are complete. We report unsupported items and data that has not moved before any closure decision. You remain responsible for the old host subscription. We do not cancel it automatically.
Dates, follow up and existing quotes
We agree the dates and changeover window in writing after checking scope, access and dependencies. No fixed delivery period applies to new enquiries.
Already accepted a quote? Your agreed price, scope and terms still apply. This offer is for new enquiries.
A useful starting point
Moving email is also a move in the way people sign in, find calendars and use shared addresses. Files, website senders and archived mail can be missed when the project is described only as changing a domain record.
We can scope a move into Microsoft 365 after reviewing the source environment. The migration plan needs to name the included data, limitations and checks before anyone commits to a changeover date.
Account for the work around each mailbox
A sole trader may have one mailbox plus years of mail stored locally. A small team may rely on shared calendars and an accounts address used by several people. Both need an inventory, but their migration scope will differ.
List website forms, scanners and applications that send mail for the domain. Include the devices used to read it. A successful data copy can still leave everyday work blocked if those dependencies are overlooked.
Inventory before promising a move
Record each mailbox, shared address, calendar and data store. Check the size and type of information to move, along with the source system and available access. Archived mail, local files and third party apps may need separate handling.
The migration plan should say what is included, what stays behind and how the team will find it afterwards.
Prepare the destination and changeover
Set up the destination accounts, licences and access before the switch. A sample migration can expose problems with data or permissions early. We agree on when users will change devices or sign in and who will receive updates.
Domain records, website forms and other mail senders need to be included in the changeover checks.
Verify the work people need to do
After the move, check mail in both directions, shared access, calendars and the devices in scope. Keep the old system available for the agreed transition where possible. Record issues and complete the handover before closing the project.
No migration should be sold as universally free of interruption. The plan should explain likely disruption and recovery options.
Compare a staged move with a single changeover
The source system, number of users and migration method affect how the move can be sequenced. A pilot may reveal data or access problems before the rest of the team changes over. Some environments require a different approach.
We agree on the old service’s availability, final data checks and the point at which mail routing changes. The plan should explain likely interruption and what happens if a check fails rather than promise that every move is invisible.
What the handover should include
The handover should record migrated accounts and data, agreed exclusions, mail tests and device access. Outstanding items need an owner and follow up plan.
Do not cancel the old service simply because the first mailbox works. The business should agree that required records are accessible and the transition period is complete before closing it.
Before you enquire
Practical answers about the scope, access and decisions involved.
Questions about this service
Will all historical email move?
That depends on the source system, data and agreed scope. We confirm exclusions and migration limits before starting.
Can we keep our email addresses?
Usually the business domain can be retained, provided you control it. The plan confirms domain access and the addresses to keep.
Can files and calendars move as well as email?
They can be included after reviewing the source, available migration method and required data. Each needs its own scope and acceptance checks.
Do you need our domain access?
The changeover normally requires agreed control of the relevant domain records. We establish ownership and access before setting a date.
When can we cancel the old email service?
After the agreed data, access and transition checks are complete. Retention needs and any records left behind must be addressed before cancellation.
Connected work
Useful next steps
A problem can sit between services. These pages help you work out which conversation to start.
