Solution
Migration to hosting you chose
Contract, access, location, subprocessors, price, capacity or service quality can all motivate a move. The migration aims for disruption you control, through a pilot, reconciliation and rollback, not for guaranteed invisibility.
Choosing where the data lives
The processing framework becomes a decision
Operator, roles, contract, locations, support access, subprocessors, transfers, retention, export, deletion and exit get written down. A lawyer reads them where interpretation demands it.
Mail cutover is controlled
Inventory, pilot, coexistence, history, calendars, aliases and shared mailboxes get reconciled. The window, the possible disruption and the rollback are stated up front.
Exit is documented
Exports, accounts, subscriptions, keys, domains and deletion requests follow a closure checklist. The evidence you get depends on what the provider can actually attest.
The new environment is held, not merely delivered
Permissions, shares and policies set on arrival rather than inherited from the previous mess. A migration is the one easy chance to clean up.
In practice
- Selection per service across operator, contract, locations, access, subprocessors, transfers, retention, export, latency, operations and full cost
- Mail and calendar migration with history preserved
- Files and shares moved, with permissions carried over rather than guessed again
- DNS cut-over planned, with propagation time accounted for
- Microsoft 365 taken in hand: policies, external sharing, dormant accounts
- Exit from the old host: extraction, account closure, subscriptions stopped
Systems involved
- Microsoft 365, Exchange and Google Workspace
- Infomaniak, Exoscale and other Swiss hosts
- Proton Mail and Proton Drive where they meet the documented case criteria
- Azure and Google Cloud, including their Swiss regions
- File servers and Nextcloud
Service lineAzure and Google Cloud →
Which workloads
The same work, against each sector’s own constraints. Every card opens the full sector.
Banking and insurance
Jurisdiction of client data
The record decides the option: operator, roles, contracts, locations, support access, subprocessors, transfers, retention, export, deletion and the exit from the former host.
Healthcare and life sciences
Chosen hosting for each dataset
Each option gets compared across purpose, roles, contract, locations, access, subprocessors, transfers, retention and exit. Permissions are reconciled during the migration.
How it runs
The reason
Weighted reasons, requirements and constraints form the decision matrix. No country, product or price decides the answer on its own.
Trial
A small group moves first, with rollback still possible and the old environment intact.
Cut-over
The rest follows in waves, with the record cut-over last, at a chosen hour.
Exit
Final extraction, accounts closed, subscriptions stopped, and written evidence that it’s done.
Test the fit: Migration to hosting you chose
Describe the context, constraints and decision you need to make. The first conversation qualifies scope, boundaries and the next useful step.
Describe the situation