Data migration is often the most complex, expensive, critical path bound and underestimated task within ERP implementations, ERP upgrades and ERP replacements. A common, time consuming and costly misconception is that it is a simple mapping of data elements from an existing system to a new system. While this requirement definitely exists, the real challenge of data migration is that individual companies often may have

• little or no experience of carrying out data conversions
• as a new one off activity, no identified tried and tested process methodology
• limited if any toolsets or technologies to assist in the process
• some knowledge of the functional use and data structures of the existing system being replaced and
• limited knowledge of the functional design and associated data structures of the new system

Example issues can consist of any to all of the following and many more

• Type Issues - data-type, field size, numeric precision etc.
• Missing / extra objects and concepts - e.g. The concept of a work order might exist in the current system but not in the target (or vice versa).
• Relationships - The entity relationship models in the current system and the target will undoubtedly be different
• Sequence Maintenance - e.g. Ensuring that the Invoice number sequence, PO number sequence etc. is maintained if required
• Master Data - This is the foundation for data migration. Getting this right is an imperative prerequisite for geting the transactional data migrated.
• Parallel development & synchronisation - Ideally data migration development should be carried out after the business process and data model for the new system is complete. It takes a skilled data migration team to handle this as a parallel activity and reduce the overall elapsed time of any implementation
• Customisations - in either the current system, the target system or both significantly increases the complexity of data migration
• Testing - testing the data migration process plus providing migrated test data for new system testing
• Data Cleansing - supporting the data cleansing effort with information. e.g. Identifying integrity issues, missing and duplicate data, orphaned records, etc.

Why Velos-IT?

Experience

Based on our heritage, Velos-IT have a history of carrying out Data Migrations both to and from

• Oracle E Business Suite,
• Oracle Enterprise One, and
• Oracle JDE World

With over 30 major data migrations completed in the last few years, we have developed a unique set of skills, processes and toolsets that significantly enhance the delivery and quality of any data conversion.

In addition to our Oracle focus we have also completed major data conversions to and from SAP/R3, Navision, Chess, Scala, etc. and covered most functional areas including Finance, Manufacturing, Distribution, Logistics, Service Management, etc..

Methodology

The only way we could have successfully completed the number of data migrations that we have carried out was by following a tried and tested process. Some data migration service suppliers view data migration as a technical task and challenge. While we recognise the fact that a large technical component does exist, we view data migration first and foremost as a functional challenge. This is reflected in our methodology.

Toolkit

The cycle time for data migration is often a key factor in an ERP project's schedule. Over the years we have constructed our own set of data migration tools that, in conjunction with the application of our methodology  and our technical and functional knowledge of the ERP design  and associated data model, provides us with the ability to optimise the cycle time for Data Migration activities.

Ultimately delivering a higher quality, shorter timeframe, Data Conversion that enhances the overall delivery of any ERP systems migration.