LIVE APPS
What changes when your app has live users?
Settle questions about changing data, integrations, and recovery before switching a live app.
Your data keeps changing
A live app may receive new records while a copy is in progress. Establish how those changes will be handled and whether a maintenance window is needed. That decision depends on the app and available source access.
A rehearsal needs acceptance checks
Discuss a rehearsal with representative data and user journeys. Include permissions, sign-in, file access, and integrations. Decide which failures would prevent a switch.
Plan communication and recovery
Decide who authorizes the switch, what users need to know, and what happens if checks fail. Recovery must account for new writes and external effects; pointing the app back at an old database may not be sufficient.
- An owner for the cutover decision
- Agreed checks before and after switching
- A maintenance or communication plan if required
- Recovery conditions and responsibility for changed data
Price the work after assessment
Live users, payments, and integrations can change the work substantially. These projects need custom scope. Neither a fixed completion date nor zero downtime is promised before assessment.
This is a planning aid, not a verified export procedure for a particular app. Access, portability, and final scope need assessment.