Migration Kit × Kenzy × Thaura

Step 1 of 5
Plan with Thaura ↗

Which Google tools does your organization run on, and what would it take to leave?

This kit inventories your stack, scores the migration effort per service, and produces a phased plan that keeps your original data untouched until the new one is verified.

Demo build: sample volumes until your inventory run is connected.

Your inventory

Tick the services your organization uses and enter rough volumes. Estimates are fine: the assessment scores effort from shape, not precision.

Leave a volume at 0 if you don't use the service. Keep and Chat have no migration API: they're flagged for manual review.

Discovery

How do you sign in to your work email?

Where do your photos live?

Is this a personal account or a company Workspace?

Roughly how much data are we talking about?

Stack assessment

Impact matrix · effort is migration work per service, not storage size
ServiceVolumeEffortEthiScoreDestination

Stack manifest complete

Nothing has been deleted. Your original stack stays live and untouched until the replacement is verified.

Migration plan

Phased so nothing is deleted before the replacement is verified. Every phase is reversible until the one marked checkpoint.

Without a key the plan below is generated by the built-in planner. With a key, Thaura regenerates it from your actual assessment, structured as JSON. The key stays in this browser session and is sent only to the Thaura API.

The divested stack

What you'd run instead, on hardware you control. This is the demo environment we stand up for the pilot: same tasks, your infrastructure.

Sandbox profile: Immich, Nextcloud, Proton and Authentik sign-in, seeded with anonymized sample data shaped like your assessment.