Intregrations
- ready to go!
Getting up and running fast is essential for any successful data migration.
Intregrations
Integration with any system
Our software can be integrated with any source and target system.
We have well-defined interfaces that can easily be applied to your systems, making your data migration successful with less effort and better quality. The application of these interfaces forms one part of the extension that will fit migFx into your context.
Our pre-built extensions contain not only the technical interface between the systems involved, but also the mapping, rules and validation that ensure that data is migrated correctly.
Should you be migrating to a standard system, chances are you could benefit from an already established extension saving you time and money.
Our pre-built integration
We have already developed a number of these preconfigured integrations
to be delivered ready to go, out of the box
Microsoft Dynamics
Oracle Fusion
Oracle EBS
Microsoft Dynamics
If you plan to use multiple Dynamics modules across your organisation, chances are that the data migration effort will be significant. Getting a head start with a preconfigured enterprise-level data migration software from us will make sure your time can be spent focusing on getting the business process right. Read more….
Oracle Fusion
Migrating onto Oracle Fusion typically include migrating into several EBS modules like HR, Finance and Purchase, etc. The overall complexity and hence the need for consistent high-quality data is greatly helped by using our solution and already established extension. Read more…..
Oracle EBS
Migrating onto Oracle EBS typically includes migrating into several EBS modules like HR, Finance and Purchase, etc. The overall complexity and hence the need for consistent high-quality data is greatly helped by using our solution and already established extension.
Generic integration
migFx is a generic tool to manage complex data migrations. As a generic tool, it must be applied to the specific situation, namely the legacy source system (to be migrated from) and the target system (to be migrated to).
We have prepared migFx for such applications by building standards around all the key elements needed. This makes it straightforward to apply migFx to any source and target system.
Unboxing integration
There are several parts that allows migFx to integrate. Together we call these parts a migFx Bridge.
A specific migFx Bridge is created to integrate migFx with a specific target system and can be used when migrating data from any legacy system.
Out of the box, a migFx Bridge contains a target map where the target system and its data requirements are already established. It also contains the integration points and message loops allowing migFx to deliver data to and receive information from the target system.
Different components
There are two main types of component of an integration for a Target or Source system, Maps and Connectors.
The maps describes the inputs, processing and outputs for either the Source data to Interface Business Objects or Interface Business Objects to the Target data. These are defined entirely within the Studio component of migFx in a standardised structure provided by that component.
The Connectors are technical components that are built to interact directly with the Source or Target system and either extract or deliver data to that system. These may take a number of forms depending on the interfaces that the Source or Target Systems expose including but not exclusively:
- API calls
- Web Service calls
- File structures
- SQL statements
Integration explained
There are several parts that together makeup migFx Integration and there several ways to apply them.
A detailed view
This flexibility ensures that migFx Integration can work with any system on any platform using any, CSV files delivered to a staging area, database or technology. migFx seamlessly invokes the Valueset Provider through a well-defined interface.
Let’s look at what the different components do and how they are positioned in migFx Integration as illustrated above, working our way from the Target System on the right to the Legacy Source System on the left.
The Valueset Provider hooks up to a well-defined migFx interface, allowing migFx to seamlessly invoke the Valueset Provider. The job of the Valueset Provider is to extract data from the Target System to populate the Valuesets defined in the Target Map. These Valuesets are in turn used by migFx to validate and complete the data flowing through the data migration.
Examples of Valuesets could be:
- A list of Product Codes known in the Target System. migFx can use the Valueset to validate the ProductCodes produced by the migration
- A list of required Interest Steps for Account products in a Bank. migFx can use the Valueset to inject missing Interest Steps for an Account product if these steps are not present in the Source System.
Also, the Metadata Provider links to a well-defined interface. This allows migFx to seamlessly invoke the Metadata Provider to import the metadata describing the Target System. This is very useful not just as a one-off to get started, but also during the project to capture any changes made to the target system.
The migrated data produced by migFx for any given Business Object is an Xml document containing all migrated data for the Business Object and its entire child Business Object hierarchy.
The task of the Data Delivery is to receive these Xml documents and place the data correctly in the Target System. The placement of data must take place using the method prescribed by the Target System (through an authorized API, direct insert etc)
The Data Delivery must handle all aspects of redelivery:
- Only process redelivered Business Objects that have not already been placed successfully in the Target System
- Clean out selected or all Business Objects in order to place corrected versions of the same Business Objects in the target System
Finally, the Data Delivery interface of migFx allows the Data Delivery mechanism to return any informational or error messages to migFx, so these can be flagged and be dealt with in a structured and supported way before another attempt is made.
The Data Delivery mechanism can take the form of files, databases etc and reside on any platform. The Data Delivery component reformats and restructure the target object data stored in xml by migFx into the format required by the target system.
The Data Delivery places the migrated data received from the Source System in the Target System using the method prescribed by the Target System (through an authorized API, direct insert etc). This coherent execution flow will improve the quality of the end to end flow by resolving dependencies and identify any issues before or when insertion into the Target System is attempted. Any issues found are returned to migFx, flagged and can be dealt with in a structured and supported way before another attempt is made.
The migrated data produced by migFx for any given Business Object is an Xml document containing all migrated data for the Business Object and its entire child Business Object hierarchy.
The task of the Data Delivery is to receive these Xml documents and place the data correctly in the Target System. The placement of data must take place using the method prescribed by the Target System (through an authorized API, direct insert etc).
The Data Delivery must handle all aspects of redelivery:
- Only process redelivered Business Objects that have not already been placed successfully in the Target System
- Clean out selected or all Business Objects in order to place corrected versions of the same Business Objects in the target System
Finally, the Data Delivery interface of migFx allows the Data Delivery mechanism to return any informational or error messages to migFx, so these can be flagged and be dealt with in a structured and supported way before another attempt is made.
The Data Delivery mechanism can take the form of files, databases etc and reside on any platform. The Data Delivery component reformats and restructure the target object data stores in xml by migFx into the format required by the target system.
The Data Delivery places the migrated data in the Target System using the method prescribed by the Target System (through an authorized API, direct insert etc). This coherent execution flow will improve the quality of the end to end flow by resolving dependencies and identify any issues before or when insertion into the Target System is attempted. Any issues found are returned to migFx, flagged and can be dealt with in a structured and supported way before another attempt is made.
When creating the Legacy Source Map, you are specifying exactly which data you are requesting from the legacy source system. Often you take what you can get – too much or too little – hard to know until you have mapped it with the data required by the Target Map.
The Legacy Source Map match the source data descriptions (metadata) with the data requirements exposed by the Target Map (through the Target Interface). As shown any migFx migration need maps completed and extensions established to facilitate mapping and data flow from source to target system. Out of the box the migFx Bridge need to be configured and setup for the systems to be migrated from and to.
If we do not have the required migFx Bridge already we will help or establish this as a part of any project using migFx.
Get in touch to learn more about Integration
Your specific Source and Target will be easily integrated with migFx.
