fbpx

Bad Data Migration is a Common Cause for Failed or Problematic ERP Go-lives

| Blog,Infor Applications Consulting and Development

Are you facing challenges with your data migration process? Here are some thoughts from the Fortude Infor M3 experts.

Plan Ahead

  • Data Migration Planning should be a key project planning activity
  • Identify the different data sources for the ERP up-front
  • Nominate Owners for each piece of data
  • Brief them thoroughly on the Cleansing & Transformation requirements from source system to M3
  • Assess the volumes of Master and Transactional data to be migrated and the time needed to extract and cleanse them
  • Plan at least 2 trial data migrations
  • Plan fall-back / contingency processes for each step
  • Define Acceptance Criteria and owners for Signoff

Develop and Test your Migration Tools

  • Use actual data for your testing
  • Consider Data Type conversions when migrating between different Operating Systems
  • Load Test you migration tools and scripts
  • Document the Data Migration Process and data mapping rules
  • Automate the data transformation where large volumes of data are involved
  • Time your data migrations to estimate the time needed for the Final Go Live
  • Freeze your solution : revisit your data migration design if any configuration changes are done
  • Develop custom templates if required for recording data during system blackout
  • Clearly define Go-No-Go Criteria for final Go-Live

 Execute your Data Migration According to the plan

  • Proactively reduce business transaction volume during the cutover period
  • Differing of production / planning of deliveries outside of cutover period
  • Ensure data accuracy through physical stock takes & advance data cleansing
  • Migrate Master Data in advance where possible
  • Ensure sufficient hardware resources are allocated for the migration.
  • Ensure timely and accurate communication between all stakeholders during the migration
  • Escalate any exceptions and review Go-No-Go Criteria with all stakeholders
  • Ensure users are allocated for entering / uploading backlogged (blackout period) transactions
  • Freeze and Archive the Source and Migrated data

Author: 
Niranjan Vaidyakularatne
Vice President – ERP Pre-Sales & Innovation, Infor Services

Related Posts

From insights to thought-leadership

View More

RPA is here to stay. Can companies remain oblivious?

Robotic process automation, simply known as RPA, came to light in the early 2000s. In the current context, its capabilities are extended with the use of several technologies such as process mining, optical character recognition (OCR), analytics, user experience (UX), artificial intelligence (AI), big data, machine learning (ML), and speech recognition technologies.

Enhance productivity with ERP integrated AI Chatbots

Due to the pandemic, businesses were forced to adapt to new norms with disruptions to usual business operations. The sudden boom in e-commerce has created new requirements. Certain products and services were in high demand, and some businesses struggled with staggering volumes of customer queries and complaints.

Quality Gates: Why all the fuss?

What are quality gates? And what is the role of a gatekeeper? Read our latest blog post by Senior QA Lead Rochana Herath as she details why investing time in identifying quality gates is important and how quality gates significantly improve the success and quality of your software projects.

Move data to Infor’s multi-tenant cloud faster and reliably with M3 Data Import Tool for Multi-Tenant (MDI-MT)

MDI-MT provides a faster, flexible, and feature-rich interface for migrating data from legacy ERP to Infor's multi-tenant cloud built on AWS.

Building business-ready applications with Infor Mongoose: 4 success stories

In the previous blog post, we discussed building low-code feature-rich CloudSuite applications with Infor Mongoose. In this article, we explore applications developed using Infor Mongoose at Fortude.

ASP.NET Core Dependency Injection and Service Lifetimes

ASP.NET Core supports the Dependency Injection (DI) software design pattern that allows registering services and controlling how these services are instantiated and injected in different components.