A checklist for your migration scope

Data and access

List the records the app stores and the relationships that matter. Identify who should be able to read and change each type of record.

• Tables, relationships, and required history
• Access rules for customers, teams, and administrators
• An agreed way to reconcile source and destination records
• A plan for records that change while work is underway

Sign-in and files

Identify sign-in providers, account recovery behavior, and how files are accessed. Password portability must be assessed for the actual source setup.

• Email/password and social sign-in methods
• Possible account resets and customer communications
• Public and private files and links
• Access checks using representative test accounts

Functions and external services

Inventory payments, email, webhooks, scheduled work, and custom backend behavior. Decide which pieces can move and which require a replacement.

• Important user journeys and external dependencies
• Callback URLs and environment-specific configuration
• Checks that avoid real charges or customer messages
• Explicit exclusions and separately quoted changes

Quote and handover

Ask for scope, acceptance checks, expected interruptions, responsibilities, and support terms in writing. Provider charges and destination accounts should be discussed separately from engineering work.