Move business email without gambling on the cutover.
Envelaro migration services plan the move around your source system, mailbox volume and acceptable transition window. Historical email is prepared first; live routing changes only after the destination is ready.
Move existing emailIncluded self-service migration
Bring your recent email with you—free.
Each eligible mailbox can copy up to 500 email messages and 500 MB from a compatible IMAP provider after the user signs in to Envelaro.
Need a larger move?
Is your old mailbox more than 500 MB?
Or does it contain more than 500 messages? We are here to support the move. Tell us about the current provider and mailbox size, and our team will help plan the right migration path.
A controlled transition
Your old provider stays available while the new environment is prepared.
Mailbox creation and the first eligible data copy happen before the final DNS cutover. That separates the time-consuming transfer from the short routing change and gives your administrator a clear validation point.
1Existing providerContinues receiving mail
2Initial copyHistorical email moves first
3DNS cutoverNew mail routes to Envelaro
Source assessment
Start with the system you have today.
Access and automation vary by provider. We confirm the supported method before promising a schedule.
Google Workspace
OAuth or administrator-authorized access, subject to source configuration.
Microsoft 365
Administrator-authorized migration using supported Microsoft access methods.
Hosted IMAP
Mailbox credentials or administrator-provided access for compatible IMAP servers.
Control-panel email
Assessment for cPanel, Plesk and other hosting environments with accessible mailboxes.
Other providers
We validate protocol support, authentication and export options before committing to a method.
Manual import
A fallback path for supported mailbox exports when direct source access is unavailable.
The migration runbook
Six checkpoints from discovery to sign-off.
Every phase has an owner and an exit condition. DNS is not the first step.
Assess the source
Inventory domains, mailboxes, aliases, groups, forwarding rules and data volume. We confirm the available access method before setting a date.
Build the destination
Create the Envelaro tenant, verify domains and provision mailboxes before changing live mail routing.
Run the initial copy
Copy eligible historical email while the existing provider continues receiving new messages.
Validate before cutover
Check mailbox counts, folders, permissions, authentication records and user access. Exceptions are resolved before MX changes.
Switch mail routing
Update MX and related DNS records in a controlled window, then confirm inbound and outbound delivery.
Delta sync and closeout
Capture eligible messages that arrived during the transition, monitor delivery and keep the previous service available until sign-off.
Define success before transfer
Know what is included, validated and handled separately.
Mailbox data
Eligible messages and folders are copied using the selected migration method. Flags, dates and folder structure are validated where the source protocol exposes them.
Addresses and routing
Mailboxes, aliases, groups and forwarding requirements are inventoried and recreated as agreed. DNS changes are staged rather than silently overwriting unrelated records.
Calendars and contacts
These are assessed separately because portability depends on the source platform, export format and supported APIs. They are not implied by an email-only migration.
Client readiness
Users receive access details for Envelaro webmail and supported mail clients. Device reconfiguration and organization-specific rollout support are scoped during planning.
No hidden cutover.
Your administrator approves the routing change after destination mailboxes and required DNS records have been reviewed.
Before we set a date
Bring us five facts. We will turn them into a migration plan.
- 01Current email provider and administrator access model
- 02Number of domains, mailboxes, aliases and groups
- 03Estimated mailbox data volume and largest mailbox
- 04Required calendars, contacts, archives or shared mailboxes
- 05Preferred cutover window and acceptable coexistence period
We will confirm the viable method, responsibilities, constraints and next checkpoint before migration begins.
Discuss your current setupMove your email without making migration your IT project.
Plan a guided move from your current provider with mailbox mapping, DNS preparation and a clear cutover checklist.
Plan your migration Migration checklist
01
Map mailboxes and aliases
02
Prepare DNS records
03
Validate SPF, DKIM and DMARC
04
Plan the cutover window
05
Switch MX and monitor
Make business email one less thing to operate.
Tell us about your domains, mailbox requirements and current provider. We will help you plan onboarding and migration.