Inventory and back up
Record versions and counts, create restorable file and database backups, and document the current user-facing paths.
Migration planning
Move an existing grid site with a tested validation and rollback plan
Inventory the current site, protect the source data, run the supported migration away from production, and compare totals and public behavior before changing live traffic or payment workflows.
Use a staged migration sequence
Production should be the final verified step, not the first place the migration is tested.
Dry run on staging
Install Million Dollar Script 3.0 in an isolated copy, run migration analysis, resolve warnings, and repeat until results are explainable.
Validate and cut over
Compare records and money totals, test representative orders and pages, approve rollback criteria, then schedule the production change.
Migration evidence to retain
Keep a concise record that another administrator can use to verify or reverse the change.
- Source and target versions, database prefixes, backups, timestamps, and responsible people.
- Before-and-after counts, sampled record IDs, payment totals, warnings, and manual corrections.
- Public page, ordering, renewal, upload, email, extension, API, and mobile test results.
- Cutover window, maintenance message, rollback trigger, rollback steps, and final approval.
Keep the legacy installation recoverable
Do not deactivate, delete, or overwrite the source installation until the migrated site is validated and the rollback window has passed. Review custom code before relying on old hooks or direct database access.
Next step
Migrate to Million Dollar Script 3.0
Start with a read-only migration review
A migration review identifies what can move automatically, what needs manual work, and what must be tested before a production quote or cutover is approved.