Case Study: Sage 200 Data Migration
Businesses are constantly growing and being bought out and sold by each other. One of the most significant projects a company can do besides a digital transformation is to merge with another company. There are so many different parts that need to be thought about, migrated or left in place and deciding which parts undergo migration is the first step.
A few things to think about are the following questions:
Do we merge our HR systems and processes or migrate employees' data?
Do we lift and shift their hardware or migrate the services to our existing infrastructure?
Do we take the historical financial transaction data to the new system or use the totals taken at a specific time?
Business mergers can be hard work, but knowing what needs to be done gives you a starting point to look out for. So many things need to be integrated during a merger, from processes to systems. Data integrations comprise much of the work, as everything is data. It can be structured or unstructured, but data remains.
Finance has to be to the penny, and we would not have it any other way. Due to a recent acquisition, we were tasked with migrating financial data of a £70 million turnover company's accounts into a much larger billion turnover business. It must be completed accurately and quickly to coincide with group reporting dates.
The migration was between two accounting packages, the source was Sage 200, and the destination was OpenAccounts. They needed a company with experience and a solid data migration methodology to complete the migration accurately.
Using our data migration method and process, we were able to build out our ETL process for their migration accurately.
Using SQL Server and SSIS, we could cleanse the data, extract it from the Sage 200 source system and transform it to the required OpenAccounts format. We kept the lineage and had the data signed off at each stage ending in a successful import out of hours.
Get in touch today to book your free consultation.