Following on from my previous article, which you can read here, I wanted to explore in more detail the use case for data integrations, and compare them with data migrations; a separate but linked process which is also crucial to future-proofing your data landscape.
MIGRATIONS
Data migration and integration refers to the process of moving data between systems and is often referred to as Extract, Transform and Load process.
Data is Extracted from the original source, Transformed to match the destination solution requirements and Loaded into the destination system.
A need for data migration may occur when an old system is being replaced and the data within it needs to be moved to a new system in one distinct exercise. However, the need could also arise where a new solution needs to run in concert with legacy systems.
In this scenario, both systems would need to be kept in sync. This can be a daunting task; any errors can corrupt data, disrupting day-to-day operations and causing issues which can be difficult and expensive to correct.
With a growing number of cloud-based technologies and internal solutions, organisations are faced with the challenge of always ensuring that the systems “speak” to each other.
This is where Integration – or a recurring and automated data migration – can help.
INTEGRATIONS
Migration and Integration will both involve mapping out how data moves across the organization.
To determine the integration strategy, the following factors will be considered:
- the granularity of the information,
- the update frequency,
- the location of the master data, and
- how other systems refer to it.
At an implementation stage, leveraging API to implement real-time integration between applications is a great strategy.
Such integration also facilitates a process of ensuring data quality over time and preventing any data corruption downstream, while maximizing real time capabilities between systems and/or platforms.
Integration also includes automation capabilities. In principle, actions on one system are easily replicated on another, without having to perform the same manual task twice. This further ensures that the data is consistent throughout.
Integration further allows for more efficient workflow processes between different systems and/or platforms. An integration layer can be configured to constantly listen for events and triggers and act in accordance with a business rule. This could take the form of one system’s data always being replicated and in sync with another, and/or a workflow process being initiated.
For support with your data migration or integration needs, please contact me at rustum.fortune@syke.tech
Rustum is a Practicing Lawyer admitted to practice in the High Court of South Africa, with a background in Engineering and Software Development. He considers himself an Agilest, and has consulted for technology companies, law firms, government, banks and the telecommunications sector, helping them innovate, while being cognizant of regulation and market practice in the TMT sector.
He also enjoys exploring the possibilities technology has to offer the Legal Industry, whether exercising a digital analysis role or performing a business, strategic, technical and legal requirements gathering role, with innovation and disruption in mind.
