Gap: Data Migration Plan

Status: 🔴 Not Started Priority: Critical (Pre-Launch) Estimated Effort: 3-5 days

What's Missing

Detailed migration strategy from legacy Strapi system including:

• Migration Scripts

  • Table-by-table migration scripts
  • Data transformation rules (Strapi → Core API schema)
  • Field mapping documentation
  • Custom field value migration
  • Form template migration

• Schema Mapping

  • Old schema → New schema mapping
  • Breaking changes and workarounds
  • Data type conversions
  • Handling of deprecated fields

• Validation & Verification

  • Pre-migration data quality checks
  • Post-migration validation queries
  • Record count comparisons
  • Data integrity verification
  • Orphaned data detection

• Rollback Plan

  • Database backup strategy
  • Rollback procedure if migration fails
  • Point-in-time recovery
  • Partial migration rollback (if possible)

• Downtime Planning

  • Estimated migration duration
  • Read-only mode during migration (if needed)
  • Communication plan to users
  • Maintenance window scheduling

• Edge Cases

  • Handling of incomplete/corrupt data
  • Missing foreign key references
  • Duplicate records
  • Special character encoding issues

• Incremental Migration

  • Can migration be done in phases?
  • Organization-by-organization migration?
  • Data sync strategy during transition period

Why Critical

1. Production Data at Risk - One migration error could lose patient data
2. HIPAA Compliance - Data integrity is required
3. Business Continuity - Extended downtime unacceptable
4. Trust - Users must trust data was migrated correctly

Current State

• Migration mentioned in overview ("data will be migrated from both the legacy Strapi system and the Intakes database")
• No detailed migration scripts
• No validation procedures
• No rollback plan
• No downtime estimate

Impact of Gap

• Cannot plan production cutover
• Risk of data loss during migration
• No confidence in migration success
• Potential extended downtime

Recommended Location

docs/migration/ directory with:

• README.md - Migration overview and timeline
• schema-mapping.md - Old → New schema mapping
• scripts.md - Migration scripts documentation
• validation.md - Validation and verification procedures
• rollback.md - Rollback procedures
• downtime-plan.md - Downtime estimation and communication
• edge-cases.md - Known edge cases and handling

Dependencies

• Access to production Strapi database
• Access to Intakes database
• Staging environment for testing
• Backup strategy

Success Criteria

• [ ] Complete schema mapping documented
• [ ] Migration scripts written and tested
• [ ] Validation queries created
• [ ] Rollback procedure tested in staging
• [ ] Downtime estimate calculated
• [ ] Dry run completed successfully in staging
• [ ] Edge cases identified and handled
• [ ] Team sign-off on migration plan