The decision was straightforward: fme migration-center was chosen solely to standardize the whole migration process, from beginning to the end. However, the beauty of migration-center was not only that the migration process works pretty much entirely with migration-center, but also in its ability to read source systems. For example, SAP migrations did not need any separate module or framework, eliminating downtime due to lack of extra processes running on SAP side even when migrations were on.
In addition, Tieto built a plugin for migration-center that helps in scanning source systems for content to be migrated and can be easily applied to any source system with little customization. The framework offered by fme made configuring the plugin a breeze.
“Thanks to the scanners, in theory, the solution scales infinitely just by deploying more and more scanners – only bottlenecked by hardware and network limitations,” says Lauri Erkkilä from Tieto.
Another strength of fme migration-center lies in its ability to work in conjunction with Archiving as a Service technology due to ready-made importer plugins: when archival packages – SIPs (Submission Information Packages) – are created for ingestion, they can be easily validated and enriched with migration-center, from simple metadata changes of strings and dates to more complex enrichments.