Back to Compliance you can evidence
A date that holds, and a documented way back
We run tenant separations and consolidations so the cutover date holds: with a tested cutover, clear communication, and a rollback plan nobody has to improvise.
30 minutes · no sales pitch · an honest read on whether we fit
A fit when
- An acquisition or divestment forces a separation on a fixed date
- Two environments need consolidating after a merger
- The divesting group restricts access and time windows
- You need a plan that also holds up to an auditor
The situation
- The cutover date is contractual, and the survey has not started yet.
- The divesting group grants access only in a limited way and with notice.
- It is unclear which data may move and which has to stay behind.
- Staff need to work on Monday, without weeks of interim workarounds.
What we do
We start with a survey that also lists the uncomfortable items: applications tied to identity, shares between the organisations, certificates and devices. From that comes a plan with waves, a rehearsed cutover, and communication that prepares users rather than surprising them. For every wave we define how we recognise success, and what we do if it is not reached.
What is included
- 01Survey and dependenciesMailboxes, files, Teams, identities, devices, and the applications that hang off them.
- 02A migration plan in wavesOrder, time windows and acceptance criteria per wave, agreed with the business owners.
- 03Rehearsed cutoverA run with a pilot group before the first real wave starts.
- 04Rollback planWhat gets rolled back, in which order, and who makes that call.
What you end up with
Complete dependency overviewMigration plan in wavesRehearsed and documented cutoverRollback plan with decision paths
Request a briefingA reply within 1 business day, from a person.