About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Inbound migration to a new managed host starts poorly when the outgoing provider still holds the only copy of VPN parameters, database backup schedules or licence activation records. An exit pack is a written request for artefacts another competent team can use to operate, cut over and audit the workload. It is intake for your migration, not the same story as an ISV customer leaving a software vendor's hosted platform — see Exit and data return when a hosted ISV customer leaves.
Why it matters
Without an exit pack, inbound engineers may rebuild settings by trial and error (editorial view), lengthening cutover and reducing dress-rehearsal value. Plan exports and contract terms early; do not rely on informal assurances alone.
Microsoft's shared responsibility page illustrates that for Azure cloud deployments customers own their data and identities; it is not legal advice and does not describe third-party managed hosting contracts. Portability is not automatic because a backup exists somewhere in a portal.
How it works
Send a dated written request (ticket plus email) listing categories and acceptable formats. Expect negotiation on secrets delivery channels. The table below is an editorial checklist, not sourced from a single vendor standard.
| Category | Examples to request | Why inbound team needs it |
|---|---|---|
| Inventory | VM names, sizes, OS versions, roles, IP addressing | Baseline parity |
| Network | VPN crypto parameters, firewall rulesets, NAT, DNS zone exports | Branch and split-horizon rebuild — deliver secrets on an approved out-of-band channel, not embedded in diagrams |
| Application | Install guides, dependency list, scheduled tasks, service accounts | Hosted redeploy |
| Data | Latest full backup, transaction log chain, file-share manifest, export checksums | Restore validation |
| Identity | AD/Azure connectors, SAML metadata, app registrations, MFA methods tied to app URLs | Post-move auth — plan retests with Planning identity, DNS and application cutovers for hosted services |
| Email and notifications | SMTP relay settings, SPF/DKIM/DMARC as used | Cutover retest register |
| Licences | Proof of licence mode, keys where permitted, SPLA reporting if relevant | Commercial continuity |
| Monitoring | Alert definitions, escalation lists | Avoid blind spots week one |
| Contracts | Notice periods, data deletion certifications | Risk and timing |
Set a deadline before cutover with enough time for decryption and restore tests in the incoming environment. Treat missing items as migration risks with named owners. A departing provider's obligations depend on contract terms, not this checklist alone.
What to choose and why
Choose standard formats (OVA/VMDK, encrypted database backup, BIND zone, IPsec parameter sheet) your incoming provider can import without one-off tooling. For SQL Server, encrypted backups may use a certificate and private key or a supported asymmetric key / EKM configuration — retain whatever protected the backup and confirm restore steps against Microsoft Learn — Backup encryption.
Choose split delivery for secrets: out-of-band secret channel. Rotate access credentials after migration (VPN PSKs, service passwords the old host knew)—do not reuse them. Retain the certificates, private keys or asymmetric keys needed to decrypt old backups for as long as those retained backups must remain restorable; rotating access credentials is not the same as discarding required backup-decryption material.
Choose verify checksums on receipt before you terminate old access. Do not ask the old host to email passwords in plain text.
Read next
Related articles you may want next.
- HostingDocumenting a hosted estate so another provider can take overDocument hosted systems so another provider can understand and operate them. Keep ownership, dependencies, configuration and recovery information current throughout the service.Read article
- HostingExit and data return when a hosted ISV customer leavesPlan tenant-scoped exports, acceptance checks, access revocation and an accurate record of active deletion, retained copies and outstanding obligations.Read article
- HostingPlanning identity, DNS and application cutovers for hosted servicesA staged plan for hosted identity, DNS and application changes, with a reporting-API example, fresh-connection tests and rollback gates.Read article
Risks and limits
Contractual export limits. A provider may restrict disk or image exports during an active contract — read the agreement and negotiate read-only export early if permitted.
Encrypted backups without keys. Useless for inbound restore.
Incomplete network docs. You may need discovery scans on your office side — only on networks you are authorised to scan; steps here are untested.
Legal. Licence terms may forbid export; escalate commercially.
Service link: How it works.
Sources
- Microsoft Learn — Shared responsibility — Azure illustration of customer data/identity ownership; not a hosting contract.
- Microsoft Learn — Backup encryption (SQL Server) — certificate, asymmetric key and EKM options for encrypted backups.
- Editorial: inbound exit pack checklist; no single portability standard opened for the full table.
Learning notes
- Exit pack is inbound intake from the provider you are leaving.
- Request inventory, network, data, identity and licence artefacts in writing.
- Verify backups and secrets before access is cut off.
- Missing items belong on the migration risk register.
- Outbound ISV exit is a different published article.
This article was originally published on .