Imports and migration

Migration readiness checklist

Use a simple readiness checklist before guided migration review so expectations stay grounded in real exports, real owners, and real cleanup questions.

Who this is for: Church admins and implementation-minded evaluators preparing for migration review.

Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es

Before you start

Use this before asking for detailed migration confidence or assuming your current exports are already ready to import.

Article metadata

Product area: imports and migration

Owner: Migration and import workflows

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Gather one representative export and list the records or workflows your team cares about most.
Escalate early if the main blocker is uncertainty about mapping, cleanup, or stakeholder confidence.

What to gather before review

Bring a sample export, the name of your current system, and a short list of the records that matter most to your team first.

If multiple stakeholders need to sign off on migration confidence, name them early instead of treating migration as a solo admin question.

What readiness does and does not mean

Readiness means your church can describe its data, questions, and likely cleanup needs clearly enough for guided review to be useful.

Readiness does not mean every field, relationship, or exception is already proven safe for one-pass import.

Escalation path

If your church cannot yet explain its export shape, owners, or cleanup concerns, use guided review instead of claiming migration readiness prematurely.

Related next steps

Read migration review basics Request guided evaluation Open Spanish version Back to help center