Goooy Bring your team across without a big-bang weekend
The migration is where most groupware switches stall. Goooy ships it inside the product: an administrator points it at the old system, maps each mailbox to a user, and watches the transfer person by person. It resumes after an interruption and skips what it has already moved, and there is no charge for it.
Where you're coming from
Two routes cover almost every case: connect to the old server over IMAP, or upload an export. Whichever you use, the mail, calendars and contacts land in the right place for the right person.
Microsoft 365 & Exchange
Connect over IMAP with the Microsoft 365 preset (host, port and TLS prefilled, with the app-password steps spelled out) and pull every folder across. Or upload a .pst export and get that mailbox's mail, calendar and contacts in one pass.
Google Workspace & Gmail
Use the Gmail preset, or take the route that needs no admin access at all: the user runs Google Takeout themselves, hands you the .mbox and .ics it produces, and you upload both.
Any IMAP server
Zimbra, Dovecot, Kerio, cPanel, Yahoo, iCloud or something bespoke. If it speaks IMAP, Goooy walks every folder in a stable order and keeps read and flagged state and the original dates.
Exports from a desktop client
Thunderbird and Apple Mail archives (.mbox), single messages (.eml), calendars (.ics) and address books (.vcf). The format is detected from the file's contents, so a misnamed export still lands in the right connector.
Your user list
Create the accounts first (a CSV bulk import, a live sync from Active Directory or LDAP, or SCIM provisioning from your identity provider), then map each source mailbox to its Goooy user.
Files and shared drives
Drag whole folder trees into the Drive from the browser, not file by file, or point the desktop app at an existing folder and let it sync everything up in the background.
Four steps, run by an administrator
You do not hand out a desktop tool, and your users do not have to do anything. It all runs server-side, in the admin console.
- 1
Connect or upload
In Admin ▸ Migrations, create a batch: pick the source, choose a provider preset or upload the export file. Credentials are sealed at rest and never handed back out by the API.
- 2
Map mailboxes to users
Each source account is mapped to a Goooy user, per data type. The batch expands into one task per user and per type, so you can bring five people over on Tuesday and the rest next week.
- 3
Run it and watch it
The engine works in bounded slices and saves its position after each one: it survives a restart, resumes where it stopped, and recognises anything it already filed, so re-running is safe. Every user shows a status, an item count and its last error.
- 4
Cut over
Point MX at Goooy when you are ready. Clients find their settings through Autodiscover, and Outlook, iPhones and Apple Mail carry on working, with the same address and the same folders.
Move a pilot group first, and keep both sides working
Nothing forces a single cutover date. Run a department on Goooy while everyone else stays where they are, and decide to continue once that department stops noticing.
- Folder structure, read and flagged state and original dates are all preserved, so a migrated inbox looks like the old one
- Re-run any user's transfer whenever you like: messages that already came across are recognised, not duplicated
- Aliases and domain aliases keep old addresses working after the move, so nothing sent to the previous address bounces
What people ask us
How long does a mailbox take?
Usually the limiting factor is the old provider's throttling, not Goooy. Because transfers run in the background and resume after interruptions, elapsed time rarely matters: people keep working in the old system right up until you cut over.
Do users lose their folder structure?
No. Every folder is recreated with its messages, their read and flagged state and their original dates, so the inbox your users open looks like the one they left.
What about calendars and contacts?
They come across too, from a .pst (which carries mail, calendar and contacts together), or from .ics and .vcf exports, which every calendar and address book on the market can produce.
Is there a migration fee?
No. The tooling is part of the product, self-hosted or hosted, with no per-mailbox charge. For large or unusual estates we'll help directly. That's what the Enterprise tier covers.
What if we want to leave again?
You can. Mail sits in a standard PostgreSQL database with IMAP in front of it, files in an S3 bucket you own, and calendars and contacts export as .ics and .vcf. That is what open standards are for.
Tell us what you're migrating from
Send us the system you're on and roughly how many mailboxes, and we'll tell you what the move looks like, including the parts that will be annoying.