Migrating all the data or just some
When planning a data migration or a data import you need to look at the nature of the data and the use made of that data.
In some cases it is vital to move all the data, for example transaction data, historical records or customer records.
In other cases the data import does not need to cover every record and the plan can allow some small percentage of poor quality data to be dropped. Examples are marketing data and details of leads were quality is perhaps more important than 100% coverage. You may even plan to not import some of the data, validating the data as it passes.
Where the data import of every record is important plan to pass some of the data migration for human inspection. Humans are, at least today, smarter than computers. You might expect to automate the data import of 90%, perhaps 95% or even 99% of data and then need to review the remainder by hand.
Your data migration plan can encompass this, using computers at what they are best at and leaving humans to handle the small number of difficult cases. Talk to us and we can help you build your plan for data migration, data import or data export.
What is a Null?
A Null and an empty string are not the same. We discuss when a Null is found in the data and how it is used.
Find Out More
Handling abbreviations in your data
We discuss how to handle abbreviations found in your source data. DataSlave offers a tool to abbreviate and indeed "de-abbreviate" data.
Find Out More