Migration from Legacy Admin
Data extraction, schema mapping, staged migration, validation, cutover.
Overview
Migrating from a legacy admin system (custom database, legacy software) to DMTR involves data extraction, schema mapping, staged migration, validation, and cutover. This guide provides a framework for planning and executing the migration.
Data extraction
Extract data from the legacy system via export, ETL, or direct database access. Identify all relevant tables: entities, positions, transfers, compliance records. Preserve audit trails and timestamps. Handle character encoding, nulls, and legacy-specific formats. Document the source schema.
Schema mapping
Map legacy schema to DMTR. Create field-by-field mapping for entities and positions. Handle type conversions, enum mappings, and structural differences (e.g., normalizing nested data). Identify gaps where DMTR has no equivalent; decide on defaults or exclusions. Document mapping rules for reproducibility.
Staged migration
Migrate in stages: entities first, then positions, then historical data if needed. Use a staging environment to validate each stage. Run parallel systems during migration to compare outputs. Plan rollback procedures. Coordinate with stakeholders on timing and cutover.
Validation
Validate at each stage: row counts, referential integrity, business rules. Compare key metrics (AUM, position counts) between legacy and DMTR. Run reconciliation reports. Fix discrepancies before proceeding. Sign-off from operations and compliance before cutover.
Cutover
Execute cutover: final sync, switch integrations to DMTR, decommission legacy for new operations. Keep legacy read-only for historical reference during a transition period. Monitor DMTR for issues; have a rollback plan. Document lessons learned for future migrations.