About this tool
Generates a practical sequence for leaving a data processing service. A parallel run adds a warning that egress is not auto-zeroed. A connected product adds a separate CRA pointer.
Session-only checklist
Cloud exit plan generator
Build a T-90, T-60, T-30, T-7, cutover, and post-cutover list. Nothing is written to an account or database.
The checklist is generated in your browser for this session. BizNavi does not save the plan.
This checklist stays in the page session. It is not saved.
Related tools
Continue with another Data Act screen. Affiliate topics are metadata only.
Supporting notes
Phases
T-90 inventory, T-60 export proof, T-30 rehearsal, T-7 freeze, cutover, then post-cutover deletion and cost reconciliation.
Browser only
Clearing the checklist removes it from this page. Refreshing also drops it. There is no saved plan.
Cutover
Cutover items cover the switch, validation, monitoring, and customer notice. They are prompts, not a runbook for a named vendor.
Limitations
The list does not review contracts and does not claim the exit meets the Data Act.
FAQ
Is the plan stored?
No. It exists only in this browser session.
What is T-90?
About 90 days before cutover: inventory, contracts, data classes, and owners.
Why a parallel-run note?
So the plan does not assume egress charges disappear during overlap.
When is CRA linked?
Only if you mark a connected product.