Database & records
Schema, relationships, and records. Agree on what is included and how the destination will be checked.
WHAT NEEDS TO MOVE?
Define the scope.
Then decide.
A backend move can involve more than copying records. These are the areas to discuss before agreeing to a project.
Users & access
Sign-in methods and permissions. Establish whether users will need a reset or other changes.
Files & functions
Storage and backend behavior. Identify what can move and what needs replacement.
Integrations & cutover
Payments, email, and webhooks. Plan how to test important flows and switch the app.
MAKE THE AGREEMENT CONCRETE
What a proposal
needs to answer.
Included work
Which data, files, behaviors, and integrations are included—and which changes are excluded?
Acceptance checks
How will records, permissions, sign-in, and important application flows be checked?
Switching and recovery
Who approves the switch, what interruption is expected, and what happens if checks fail?
Handover
Which notes, access details, and support terms will be part of the agreed delivery?
What is outside the initial offer?
App redesigns, new features, and unrelated bug fixes require separate scope. Other source platforms need their own assessment. Provider fees are separate from engineering fees.
We do not collect migration credentials in the initial inquiry. Secure access arrangements must be established before technical work begins.
Use the scope checklist ↗START WITH A CONVERSATION
What would you like
to change?
Tell us what you have built and why you are considering a move.
Discuss my appNo account. No credentials. No payment.