migFx data migration process
An agile data migration cycle that enables fast progress, cross-functional collaboration and high quality.
People, process and tools
Ask yourself – do I have the right people, the right process, and the right tools for my data migration?
Process and tools enable people to optimise their performance – get the job done faster, cheaper and better.
Remember that tools and technology make a great servant and a terrible master, so tools are only valuable if they support and enable better performance.
Make sure that whatever process and tools you choose for your project empowers people and increases productivity.
Data migration process
We view the data migration process as a two-way process. The logical way and the physical way.
The logical way goes from the target system data requirements back to the source systems existing data.
The physical way is the actual offloading data from the source system, transforming them, and inserting them into the target system.
Basing the migration on the Target Map is a key quality of migFx. After all, the target system is what remains – the source system is left behind and usually decommissioned.
Cross-functional teams are crucial
A key element of a process applying the agile approach is the building of cross-functional teams.
It is important that both technical and business resources are applied to the migration process so that issues can be ironed out fast as requirements continues to develop.
migFx supports team collaboration by providing a mix of functionality that enables all stakeholders to gain a common view of the project. The business subject matter experts can actively participate in the migration process from defining the requirements right through to the end by reviewing and if necessary correcting the results.
- Studio allows the structured recording of both Target and Source data structures and content, together with the business rules that govern them, in an environment accessible to the subject matter experts.
- Engine rapidly produces executable code from the definitions recorded in the Studio to enable the processing of real source data into a form that can be tested in the target system, the code is controlled in this execution by the Director which also maintains an audit trail of the execution runs.
- Finally, Tracker enables both the subject matter experts and the functional consultants to review the results of the transformation process and decide what corrective action is required where errors are detected. It also enables the project manager to review the results of the processing to produce detailed and statistically sound reporting to communicate to the remainder of the programme management.
migFx supports the process
The typical iteration flows in six steps. Each step getting you closer to a better data migration.
... the process
- Mapping is done in Studio. New Business Objects may be added, existing business objects may be modified
- New code is auto generated by Engine
- New manual rules may be added or existing modified
- The code is deployed to the Director and the migration is iterated as needed
- The migration results and events are shown in Tracker
- Feedback flows back and mapping and can be modified in Studio – the cycle repeats
Working with migFx
Focus on Business Objects
Providing a logical partitioning and reference for all.
The root Business Objects will naturally divide the migration tasks into teams.
Map a small part of a Business Object in Source- and Target Map to quickly get a fast, iterative cycle up and running.
All events and data are grouped by Business Object giving you a perfect line of sight.
Iterate, iterate, iterate
Your mapping is validated so you can be confident that it is consistent.
If you make mistakes the validation will point them out to you – simply undo your changes and go back to where you were.
Correct mapping, publish, generate, build, deploy and retest is done in a matter of minutes.
The ease of iteration is unique to migFx and lets you progress stepwise, gradually progressing with confidence.
The different parts of the process
Incremental
Complex data migrations are often – well, complex. The traditional approach takes a long time from initial specification to any implementation. Often many design and implementation choices are made too early from which it is difficult and risk-prone to deviate.
Using migFx, it is straight forward – and indeed best practice – to get operational extremely fast. You don’t need a complete overview or full understanding to enter an agile loop. Just start immediately by mapping just a small part of one or more Business Objects, generate the code and start iterating.
The consistency and uniformity imposed by migFx enables the incremental addition and enhancement of Business Objects. This process is perfectly aligned with the most natural and indeed unavoidable way ahead in any data migration project.
You will find your data migration team continuously and confidently iterating the agile loop – typically many times a day. This incremental approach to the challenges takes the quality of the data migration to an entirely different level – and leaves you with a data migration team feeling empowered and successful.
Progress over time
The data migration project will gradually progress over time. Step by step (sprints) adding more coverage (business areas, objects…) and depth to the already defines objects, validations, and rules.
The project at an early stage will be able to show results in limited areas with limited quality, but as more data and rules are added coverage and quality will increase.
