Two to three working days
A founder, a few staff and a shared inbox. Cutover on an evening, everyone signed in the next morning.
Email and data migration
Microsoft 365, Google Workspace, Exchange, cPanel and IMAP hosting, Zoho, Dropbox, Box, OneDrive and SharePoint. We move mail, calendars, contacts, files and shared drives while your team keeps working, switch over in a window you choose, and close only when the counts match on both sides.
Platforms we migrate
Product names and logos belong to their respective owners. Guanacos Tech is an independent consultancy; we run each vendor's own migration tools as a service.
The routes we run
Most moves we run end in Google Workspace or Microsoft 365. Each route has its own tools, limits and losses, so each has its own page.
Mailboxes, calendars, contacts and tasks, OneDrive to My Drive, SharePoint sites to shared drives, Teams channels to Chat spaces.
See this route →Mail from cPanel, GoDaddy, Hostinger, HostGator, Zoho Mail or any IMAP server, with the folder tree kept as labels and the domain authenticated properly.
See this route →Gmail, calendars and contacts into Exchange Online, Drive and shared drives into OneDrive and SharePoint, Docs converted to Office files.
See this route → Tenant ATenant BWorkspace to Workspace or Microsoft 365 to Microsoft 365, for an acquisition, a split, a rebrand or a domain change.
See this route →Dropbox, Box, OneDrive and SharePoint into Google Drive and shared drives, or into OneDrive and SharePoint, with sharing mapped by user and group.
See this route →Retiring the server in the closet: mailboxes and calendars to Google Workspace or Microsoft 365, file shares to Drive or SharePoint, in stages if needed.
See this route →What we move
A migration that moves mail and forgets the shared drive is half a migration. This is what goes where on the two most common destinations.
| What | Into Google Workspace | Into Microsoft 365 |
|---|---|---|
| Full history; Outlook folders become Gmail labels | Full history; Gmail labels become folders | |
| Calendars | Events including recurring ones; Teams meeting links kept as links | Events and attendees; room bookings and shared calendars rebuilt by hand |
| Contacts and tasks | Contacts, and Microsoft To Do tasks from Exchange Online | Contacts (up to three addresses each) |
| Shared mailboxes and groups | Shared mailboxes become Collaborative Inboxes; distribution lists become Google Groups | Google Groups become distribution lists or Microsoft 365 groups |
| Personal files | OneDrive and Dropbox to each user's My Drive, in their existing format | My Drive to OneDrive; Docs, Sheets and Slides converted to Word, Excel and PowerPoint |
| Team files | SharePoint sites, Dropbox team folders and Box to shared drives | Shared drives to SharePoint sites or Teams |
| Sharing and permissions | Mapped by user and group from an identity map | Shared drive permissions mapped; file-level sharing on request |
| Chat | Teams channels become Google Chat spaces | Planned per project |
Based on Google's and Microsoft's own migration documentation, checked October 2026. Limits change; we confirm them for your tenant during discovery.
What usually does not survive
Every vendor tool leaves something behind. Knowing it up front is the difference between a plan and a surprise on Monday morning.
The tool changes with the route. The sequence does not, and it is what keeps mail flowing.
Every user, alias, shared mailbox, group, calendar resource, file library and integration that sends mail, with sizes, and the losses list for your route.
Accounts, aliases and groups created and licensed on the destination before any data moves. The vendor tools need them to exist.
The destination's SPF and DKIM published while the old system is still authorized, so receivers trust the new platform from its first message.
A few users first, then the bulk of the history copied in the background while everyone keeps working on the old system.
MX changed at the hour you choose, both sides receiving during the switch, and a final sync of whatever arrived in the last hours.
Message and file counts compared per user on both sides, the old system kept read-only for a period you set, and a one-page runbook for your next admin.
Timeline and pricing
Typical calendar time from kickoff to reconciled hand-off for mail, calendars and contacts. Large file libraries add seeding time in the background, not downtime.
Two to three working days
A founder, a few staff and a shared inbox. Cutover on an evening, everyone signed in the next morning.
About one week
Groups, shared mailboxes and a file library come into play. One seeding pass, one evening or weekend cutover.
Two to three weeks
Seeded in waves by department with a pilot group first. The MX change still happens once, in one window.
How we scope, quote and invoice is on how we work.
Before you decide
Microsoft 365, Exchange Online and on-premises, Google Workspace, personal Gmail, cPanel, GoDaddy, Hostinger and Zoho mail, and OneDrive, SharePoint, Google Drive, Dropbox and Box files.
No. The old system keeps receiving until MX changes, both sides receive during the switch, a final sync catches the last hours, and counts are compared before we close.
Sign in once, set up 2-step verification, and attend a short session. Their mail, folders, calendar and files are already there.
Not by us. Google's import tools and Microsoft's Migration Manager copy the data. The old system stays read-only for a period you choose, then we help you close it.
SPF, DKIM and DMARC go live on the destination as part of the move. Our email deliverability service continues from there if you want it.
No. Guanacos Tech is an independent consultancy with Google-certified engineers. You buy the licences, we do the work, and we answer to you.
Thirty minutes, free. Bring the user count, the current platform and roughly how much is in the shared files, and you leave with a route, the known losses and a fixed price.