All the functionality you need

Build Business Objects, map data and assign rules, generate and execute code – view and track results


Studio provides the functionality needed to ensure a very high degree of consistency and coherence in the mapping. Most importantly, the Studio facilitates and enforces mapping of an extremely structured nature, serving as input to the Engine that generates the migration code.

This guarantees a comprehensive and consistent interface to establish business objects and apply rules and validation criteria. Using the Studio, a team of business experts can collaborate to produce, cross-reference and validate the mapping.

Apart from providing the platform to produce structured and standardized mapping, Studio also have a high degree of focus on productivity and collaboration. The Studio is backed by a central repository, users can take ownership of mapping artefacts by check-in/checkout/getlatest mechanisms and the Studio itself is a rich, multi-document application allowing the user to work efficiently.


Engine generates the code to be used by Director to execute the data migration, based on the mapping done in the Studio.

This ensures:

• Complete consistent between the mapping and code
• Uniform and high quality code

The quality of the code is such that it is never manually changed. If, for some reason, the code does not produce the desired results, then correction is made by modifying the mapping and re-generating the code.

The mapping from Studio may specify that certain rules must be implemented manually. The generated code contains stubs making their implementation easy and clearly visible.

The generated code and any manual rule implementation is available in Visual Studio with the full capabilities of this environment, like automatic code-completion of items specified in Studio and generated into the code.


Director is the execution manager. It activates the generated Engine code to execute the data migration. Through the Director, the user loads source data, populates value sets, executes the data migration and offloads the target data produced.

Use of the Director means that it is possible to iterate in a very fine-grained manner. It’s possible to iterate all Business Objects that have generated a specific event during migration, to iterate a specific Business Object, etc.

The Director is a client server application. The client component is used by one or more users to monitor and execute migration jobs in the server component.

The Director supports the operation and execution of several data migration projects across multiple servers.


Tracker is a web application that is easily accessible to everyone involved. It shows the migration results and any events raised, including baseline comparisons that reveal trends since the last iteration.

The application shows detailed information for each migrated business object, helping the user analyse the results and track any issues – searching or drilling down to a specific business object, etc.

Tracker also keeps track of the state of events (new, fixed, accepted, recurring etc.), any comments, and makes possible the assignment of issues to users and teams.

If specified in the Studio, certain data requirements are shown in the Tracker for business users to provide data, typically for translations between source- and target systems.

An agile data migration process that enable fast progress,
cross functional collaboration and high quality


No data migration exists in a world of static and well-defined requirements. The reality is a moving target, as the target system itself is undergoing changes – because the data migration uncovers the gaps between the source- and target systems.

Using traditional tools (such as ETL) many projects bog down over time as both mapping and implementation struggle to keep up with changing requirements. Often the implementation drift away from the specification – thereby losing the only instrument available to ensure the data migration is aligned with the business requirements.

Using our Solution, the process of modifying the mapping, generating the code and iterate the migration is fast and agile. The Solution ensures consistency between mapping and implementation. The mapping is the implementation – always relevant, valuable and the only place where requirements are implemented and documented.

The rich support for cross-reference, validation and what-if scenarios in the mapping enables constant sight of the ever-moving target.

Uniform code and handling of events during the migration iterations ensure that the implementation always behaves in the same way throughout the lifetime of the migration project – regardless of the changes made.


Complex data migrations are often – well, complex. Applying the traditional approach it 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 our Solution, 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 our Solution 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 competent.


Fundamental for our Solution is the fast and agile feedback loop. The complete support by the framework components involved makes the speed and agility of this loop impressive.

At the same time, consistency and uniformity ensures that every iteration of the loop augments quality and that everybody involved from mappers to business users stay well informed and confident that any regression is caught immediately.

Data Migration Process

The typical process flows in six steps:

  1. Mapping is done in the Studio. New Business Objects may be added, existing business objects may be modified
  2. New code is auto generated by Engine
  3. New manual rules may be added or existing modified
  4. The code is deployed by the Director and the migration is iterated as needed
  5. The migration results and events are shown in the Tracker
  6. Feedback flows back and mapping and can be modified in Studio – the cycle repeats

Each step getting you closer to a better data migration.


We have put together a summary of our Solution in a short Factsheet and added a longer document called Concepts – both ready for you to read offline, print or share with colleagues.


hopp FactSheet 1.58 MB 7 downloads


migFx Concepts 4.67 MB 10 downloads