Accounts and groups
Entra ID users, groups and licenses, matched between source and target.
Dynamic groups and distribution list members are out of scope. Microsoft 365 migration
Tenant migration with planning, control and traceability.
Primora TenantFlow is Primora’s platform to plan, run and track Microsoft 365 tenant-to-tenant migrations and Zimbra to Microsoft 365 migrations.
Mergers, acquisitions, divestitures and environment consolidation, with an assessment before every migration and a record of what was done.
Illustrative
The challenge
Migrating a tenant is more than copying mailboxes.
Identities, groups, permissions, files and conversations need to arrive together and in the right order. Without visibility, problems show up on the first day of use.
Hidden dependencies between accounts, licenses, groups and permissions that only surface mid-migration.
01Side spreadsheets to track who has migrated, what failed and what is still missing.
02Limitations found too late items Microsoft does not allow to migrate that nobody warned about.
03No record of who ran each step and what the result was.
04
Microsoft 365 → Microsoft 365
From source tenant to target, one module at a time.
Every module goes through the same phases. Migration is only released after an up-to-date assessment.
Modules
What is migrated in each module.
The recommended order starts with accounts, because every other module depends on them.
Exchange Online
Email, calendar, contacts, tasks, inbox rules and automatic replies, in user, shared, room and equipment mailboxes.
Incremental sync for email.Teams
Teams, channels, members, messages with original date and author, and chats.
Chats from the last 8 months.OneDrive
Drive provisioning in the target and migration of each user’s files.
SharePoint
Lists, libraries, permissions and sensitivity labels, preserving author and created/modified dates.
Older file versions are out of scope.Devices (Entra ID)
Permission adjustment, transition and cleanup of devices.
Run by the operator, with confirmation at each step.Zimbra → Microsoft 365
An agent in your environment, control in the platform.
For on-premises Zimbra, migration is done by a Primora agent installed in your network. It reads Zimbra and writes directly to Microsoft 365; the platform coordinates and tracks.
No open ports
The agent only opens outbound HTTPS connections. No port needs to be exposed to the internet.
Content straight to Microsoft 365
Messages and contacts go from the agent to your tenant. The platform only receives progress.
Trusted agent
Signed package, one-time enrollment code and its own credential for each agent.
Restricted access in the target
Writing to Exchange Online uses a certificate and permission scoped to the project mailboxes.
Control
Every step with an owner and a record.
TenantFlow guides the operator: it shows what blocks the migration, why, and what the next step is.
Assessment before migrating
Each module flags risks and limitations before running; an outdated assessment blocks the migration.
Simulation
Run a simulation to check the expected result before the real migration.
Access roles
Owner, administrator, operator and viewer roles for each organization.
Isolated data
Each organization sees only its own projects, with isolation enforced in the database.
Activity trail
Who ran each step, in which module and with what result.
Reports
Export to CSV, XLSX and PDF for tracking and accountability.
FAQ
Questions we often hear.
Want to see TenantFlow applied to your scenario? Our team shows the platform and assesses your environment.
Talk to a specialistEntra ID accounts and groups, Exchange Online mailboxes (email, calendar, contacts, tasks, inbox rules and automatic replies), Teams (teams, channels, members, messages and chats), OneDrive, SharePoint (lists, libraries and permissions) and the transition of Entra ID devices.
Yes, and the product shows it before migrating. Examples: distribution list members, dynamic groups, Teams chats older than 8 months and older SharePoint file versions. Each module’s assessment flags these items so they can be handled in the plan.
A Primora agent is installed on a Linux server in your environment. It only makes outbound (HTTPS) connections, reads Zimbra without changing it and writes directly to Microsoft 365. The platform coordinates and tracks the work without receiving mailbox content.
Email (folders, messages, attachments, dates and flags) and contacts. Drafts, Briefcase, tasks, distribution lists and shares are not yet part of the platform and are handled in the migration project run by Primora.
No. Entra ID device tasks (permission adjustment, transition and cleanup) are run by the operator, with confirmation at each step.
Each module has progress tracking, an activity trail and reports exportable to CSV, XLSX and PDF.
Plan your migration before moving the first item.
Book a demo and see Primora TenantFlow applied to your migration scenario.
Or write to comercial@primora.com.br