Begin with a bounded discovery phase covering code, schemas, data samples, exports, integrations, traffic, operations, owners, risks, and extraction tests. The output is a migration inventory, architecture, mapping approach, assumptions, exclusions, proof points, phased estimate, rehearsal plan, cutover controls, and legacy-retirement decision.
Use discovery to turn unknowns into a bounded delivery plan
Start with a time-bounded discovery phase focused on the uncertainties that could invalidate the project: source access, extraction, data meaning, critical business rules, and integration feasibility. The useful output is evidence and decisions, not simply a longer feature list.
Separate confirmed work from assumptions, dependencies, and unresolved risks. Show which findings could change the estimate and who must resolve them. Plan a representative migration rehearsal before committing to final cutover, and include operational acceptance, historical access, and legacy retirement. A fixed launch promise made before these questions are investigated is difficult to rely on.
What to check before deciding
- Test source access and extraction feasibility first.
- Document scope, assumptions, exclusions, and decision owners.
- Estimate discovery, build, data, validation, and cutover separately.
- Tie launch readiness to tested outcomes and agreed unresolved risks.
