TenantShuttle · the inside view: the clouds · diligence to integrationKnow the cloud estate you are taking on.
A data room lists the main subscription and the systems somebody remembered. TenantShuttle reads how the company actually uses its clouds, read-only and through access its own administrators grant: every account, subscription and region, every setting, identity and permission, what it spends and what it is committed to. Then it shows where each part of the estate could go, and plans the move without taking over a name or merging an account that nobody approved.
Microsoft Azure, Entra ID and AWS · runs on your own computer · available on request
The deal and the integration plan rest on the real estate
What the clouds cost, what they commit you to, who can reach them and what would block a move all change the price and the plan. They are rarely in the handover documents.
Before you sign
What runs where, who has owner-level access, what it costs and commits you to, and which settings were changed from the provider's defaults, each with the document it came from.
On day one
Which accounts, subscriptions and identities you now own, which guardrails apply, and who is told when something goes wrong.
Through integration
A destination for each workload, a move plan with every clash and held item in view, and a comparison of collections to see what changed along the way.
One document that says what you are inheriting
The tenant and its domains and licences, the organisation and its guardrails, the frameworks the company is measured against, who has owner-level access, who is told when something goes wrong, where the data lives and who can reach it, and every service and how it is set up. A workbook lists every record and a complete export keeps every raw document.
- Read-only: every request is checked against a reviewed list of reads before it is sent
- Access the company's administrators grant with scripts they read and run, and can take back
- Settings recorded, secret values never kept
What could not be read, said plainly
A list the access did not allow, a region a guardrail keeps out, a service not offered in a region and a service nobody set up are different things, and the report says which. Nothing is quietly left out, and nothing is reported as found when it was never read.
Where each part of the estate could go
Each service in use is named by what it does, then matched in a catalogue for each of nine destinations: the service that does the same job, how well it fits, how to move it, what carries over and what does not, the effort and the downtime. Every path cites the vendor pages it was checked against.
- AWS, Microsoft Azure, Google Cloud, Cloudflare, Oracle Cloud, DigitalOcean, Hetzner, Akamai and on-premises
- Blockers and the capabilities a destination has no equivalent for, named up front
A move plan that never takes anything over quietly
Before anything runs, every name the move would create is checked against what the destination holds, the cloud's names that must be unique across every customer, and the plan itself. Each clash comes with ranked fixes, and anything that would overwrite, merge or put resources into an existing account waits for a named person to approve that one item, after reading what exists, what will change and what cannot be undone.
Planning is available today. Carrying out moves is in development, and each path is proven in a lab before it is offered.
Where TenantShuttle fits in due diligence and integration
TenantShuttle starts as soon as the target grants read-only access to its clouds, and stays useful until the last workload has moved. See every stage of a deal.
Due diligence
- Where the target grants read-only access, read its clouds: every account, subscription and region in scope, and what could not be read
- Weigh what the estate costs and commits you to, and who has owner-level access
- See the paths to your own clouds, with the blockers named, before the integration is priced
Integration
- Collect again on day one and compare: what was added, removed or changed since due diligence
- Know which accounts, subscriptions and identities you own, and which guardrails apply
- Choose a destination per workload and plan each move with every clash and held item in view
- Log what needs deciding in HouseGRC, with an owner and a date
Taking on a cloud estate?
TenantShuttle is available on request. Tell us about the deal and the clouds involved.