Skip to content
Xferity

Migrating Off Legacy MFT — A Practical Approach to Platform Replacement

Migrating Off Legacy MFT

Section titled “Migrating Off Legacy MFT”

Legacy MFT migrations fail for one of three reasons: trying to migrate everything at once, not validating partner connections before cutover, or underestimating how much configuration is buried in undocumented GUI state.

Before you start

Section titled “Before you start”

Inventory first. List every active flow, every partner, and every schedule. Do not start migrating until you know what you are migrating.

Identify what is actually in use. Legacy MFT systems often have dozens of configured flows; many are inactive. Confirm which ones actually run before building equivalents in Xferity.

Identify embedded secrets. Legacy systems store passwords and credentials in GUI-accessible config databases. Plan to extract these and put them into proper secret references before cutover.

The migration approach that works

Section titled “The migration approach that works”

Migrate flow by flow. Not partner by partner. Not all at once.

  1. define the Xferity partner and flow equivalent for one active flow
  2. validate configuration
  3. run diagnostics against the live partner endpoint
  4. run the flow manually once in parallel with the legacy system
  5. confirm the outcome is equivalent
  6. cut over that flow to Xferity
  7. monitor for one production cycle
  8. move to the next flow

This approach produces a clean validation record for each flow and limits blast radius.

Common migration blockers

Section titled “Common migration blockers”
  • SSH host keys stored in legacy GUI: extract and add to partner known_hosts or configure fingerprints in Xferity partner definitions
  • Certificates in legacy keystore: export and import into Xferity Certificate inventory
  • PGP keys in legacy keyring: export and import into Xferity PGP Key inventory
  • Schedules using legacy cron syntax: Xferity uses six-field cron with seconds — translate accordingly
  • Cleanup rules: legacy systems often have file archiving and deletion rules; carry these over explicitly in flow config
Section titled “Related pages”