ActiveSystemActiveSystem

Products > Adoption support

iTrans Data Migration

iTrans is the migration tool used to move data from existing systems into MFA when MFA is adopted. It is used for the migration when the customer requests it, and customers who migrate on their own receive deliverables built from the same mappings and validations. Support for customers who migrate on their own (a script package) can be used now, and the connection that loads data into MFA is being prepared to match adoption schedules.

Migration process

Every source follows the same process.

  • Import: Source data is read and kept as a snapshot of the import time.
  • Profile: Row counts, fill rates, and value distributions are reviewed.
  • Map: Field and code value correspondences to MFA are defined and approved.
  • Validate: Transformation and validation run without loading to find failing records.
  • Load: Records that pass validation are loaded, and failing records are quarantined.
  • Reconcile: Counts, totals, and references are compared between source and target to judge the result.

Key features

  • Source connections

    Existing databases are accessed read-only, and on databases where write privileges can be verified, accounts with write privileges are refused. Excel and CSV files and Google Sheets can also be imported, and later steps work from the import snapshot so they repeat without reconnecting to the source.

  • Mapping and approval

    Field correspondences between source and MFA are defined on screen and managed as versions. Authors and approvers are separated, and a production load does not start while unresolved code values remain.

  • AI mapping suggestions

    AI drafts field and code value mappings, and staff review and approve them. Values classified as personal data are not included in AI requests, and the same process works with AI turned off.

  • Quarantine and reprocessing

    Records that fail validation are quarantined and reprocessed alone after the cause is fixed. An interrupted run resumes where it stopped, and repeating a run does not duplicate data.

  • Rehearsal runs

    Rehearsals run against a non-production target before the production migration, and their results can be cleared and run again. A mapping table between legacy identifiers and MFA identifiers keeps references connected.

  • Reconciliation and sign-off

    Counts, totals, and references are reconciled across source, staging, and target, and exceptions go through approval. The cutover report contains no business data values.

Support for self-managed migration

Customers who migrate on their own use the same mappings and validations. In that case iTrans does not load data; it exports a package of mapping specifications, validation, load, and reconciliation scripts, and the identifier mapping table.

Working with MFA

  • Changes made by a migration run do not generate emails, notifications, or outbound interface messages, and the business events for those changes are held and processed after the migration.
  • Data change audit records are kept per migration run.
  • Data created by real users, not by the migration, is not overwritten.
  • Target structure lookups and reconciliation use a dedicated read-only migration account.