Email migration
Move mailboxes, aliases, calendars and domains with attention to reachability and user guidance.
View email migration
Migrate & switch
IT migration built around your daily work.
You want to move systems while keeping track of email, documents and ongoing work. Radorfa maps your environment and dependencies, plans the move and tests the result with your team. Recovery and aftercare are agreed in advance.
More than moving data
Dependencies determine migration risk
Accounts, mailboxes, shared files, devices, DNS, applications, integrations and supplier agreements all interact. We make that chain visible before the first change, then test and validate the transition in logical stages.
Exchange Online
Bring mail flow, security policy, shared mailboxes and management into a controlled Microsoft 365 setup.
View Exchange managementSharePoint & OneDrive
Migrate files while preserving structure, ownership and appropriate access.
View file migrationOdoo migration
Prepare databases, modules, custom work, integrations and user acceptance for a new Odoo environment or version.
View Odoo migrationSwitch IT partner
Transfer documentation, accounts, equipment, contracts and management safely from the incumbent.
View IT transition
Migration path
Six checkpoints around transition
The exact plan varies, but these checkpoints remain. Go/no-go moments and responsibilities are agreed in advance.
Inventory
Capture source, destination, volumes, permissions, dependencies, exceptions and contractual access.
Design
Define sequence, mapping, security, communication, acceptance criteria and fallback.
Pilot
A representative group tests data, access, devices, integrations and daily workflows.
Prepare the transition
Planning, a temporary change freeze, backup and communication are ready. Responsibilities for the transition and checks are clear.
Validate
After switching, verify data, mail flow, permissions, synchronisation and agreed business scenarios.
Support and closure
Track remaining points, support users and retire the old environment only according to plan.
Practical check
What we need before scheduling
This information supports a realistic plan and prevents critical dependencies surfacing only during the transition.
- Which systems, mailboxes, files and integrations are in scope?
- Who controls admin accounts, domains, licences and contracts?
- Which processes may be interrupted, and when?
- Which data and scenarios define acceptance?
- Which source remains available for controlled fallback?
- Who makes each go/no-go decision?
FAQ
Frequently asked questions
Clear answers about the scope and first step for this route.
Can migration happen with no interruption at all?
That depends on source, destination and dependencies. We do not promise zero interruption without analysis; we do plan how impact is limited, communicated and controlled.
Why is a pilot necessary?
A pilot reveals unexpected permissions, device settings, integrations and user scenarios before the full organisation transitions.
When is the old environment retired?
Only after agreed validation, retention requirements and the fallback window have been completed according to the migration plan.
Turn this route into a practical plan
We start with the current environment, business impact and dependencies. You will know what needs to happen first and why.