Data Migration & Conversion Services
Data Migration is the process by which data is transferred from one or more data sources to one or more target repositories. Data Migration from a legacy system to SyteLine or CSI requires an impeccable, in-depth knowledge of the SyteLine and CSI schema. There’s no way around that. Fortunately, we know the schema like the back of our hands. Not just table and field names. How they’re used, their conversion, storage rules as well as usage. And we have the tools and know-how to carry it out.
Every year since 2008, we’ve taken on two to four of these types of data migration projects. On average, they are completed within 6 months. We have not experienced a failure yet. Part of the credit for our perfect batting average goes to the users. By sheer luck, really, every company we’ve ever worked with has accepted our recommendation to assemble an internal team dedicated to the project. And we really mean “dedicated”. Initially, we might be on site fairly frequently. However, most of the work can be and usually is done remotely which saves our client having to pay for our travel and lodging expenses.
There are many considerations that go into a Data Migration project:
Are there power users that can be relied on to be on the core implementation team at your company? For the next few months? As well as a single highest ranking individual accepted by all as the “Sponsor”? The buck stops at her or his desk. They call the shots and steer the project back on track when it faces impediments including but not limited to personnel availability, politics, hardware or software resource needs.
Is the legacy system the Live business ERP system and when will cut-over be performed? Is there a natural window of opportunity ahead? A long weekend?
How much time will be needed to perform the migration prior to the cut-over?
How much data is to be brought over and what can safely be archived for read-only access?
Is there relatively static data that can be migrated in advance – months ahead?
Is a direct transfer from the legacy database to the SQL Database feasible? Will dumping to and loading from an intermediary format such as CSV files be necessary?
Is this part of the first-time implementation of SyteLine or CSI, or will this be a merger with an existing SyteLine / CSI system?
Is SyteLine or CSI multi-site?
What will “conversions” or transformations of data be necessary to support the business going forward?
Any required SyteLine or CSI data elements which the legacy system lacks or does not track?
These considerations necessitate lots of advance preparation and collaboration among the stakeholders – the users on the one hand and us technicians, business analysts and consultants on the other. You can expect the effort to be expended on:
the budgetary estimate and projected timeline using tools such as Microsoft Project
getting to know the various players on both sides. Assigning roles and responsibilities
remote access to the network
analysis and data mapping
utilization of our homegrown data migration tools – such as the Abbey Code Solutions proprietary, amazing, blazingly-fast “Parts, and Bill of Materials Bulk Loader”
development of data migration scripts tailored to the users’ needs
two or more trial migrations and benchmarking
testing, tweaking, and validation
knowledge transfer
final cut over
We would be remiss not to state that we do perform a pre-qualification on our own dime. To assess the suitability of the project. We accept the vast majority of requests. In many cases, we’ve become life-long partners of our clients. Some projects, inevitably, have had to be turned down. On one or more of many possible grounds. We might have had our hands full at the time. Impossible deadlines. No dedicated internal team is a big no-no.
