melsoftware / OmniMailing
Migrate to OmniMailing
Move email with attachments, calendar events and contacts to your own server. Start with a few mailboxes and review your data before switching the whole company.
What you can move
| Source | Data | What to prepare and check |
|---|---|---|
| Microsoft Exchange Server | Email with attachments and the primary calendar. | IMAPS and EWS access. Check recurring events and the import date range. |
| Microsoft 365 | Email with attachments, calendar events and text history from supported Teams chats. | A Microsoft Entra app with read permissions. Teams history is a read-only archive. Channels and chat attachments are outside its scope. |
| Yandex 360 for Business | Email with attachments and calendars. | IMAP access and separate app passwords for email and calendar. |
| Zimbra | Email with attachments, events and contacts. | A folder of TGZ archives. Use a content-only export (meta=0). |
| Outlook PST | Email with available attachments, events and contacts. | A PST file or a folder of archives. Remove PST password protection first. |
| Google Workspace | Email with attachments, the primary calendar and personal contacts. | A service account with delegated access. Check folder placement as custom Gmail labels are outside the import scope. |
Access and data coverage depend on the source and its configuration. Check shared mailboxes, permissions and non-standard calendars separately in the pilot.
How to run a pilot
- 1. Map employeesPrepare OmniMailing mailboxes and assign each data source to its recipient. Use a CSV for a batch.
- 2. Check readinessThe wizard checks destination accounts and shows the plan and warnings before copying.
- 3. Move a few mailboxesReview folders, attachments, events and contacts. Then schedule the rest of the migration and the mail cutover.
Tell us what you use today
Share your current system, approximate mailbox count and the data you need to retain. We can then define what to verify in the pilot.
Discuss your migration Pricing and trial