{"id":10264,"date":"2017-03-24T07:45:25","date_gmt":"2017-03-24T07:45:25","guid":{"rendered":"https:\/\/fortude1.wpenginepowered.com\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/"},"modified":"2026-05-07T05:51:56","modified_gmt":"2026-05-07T04:51:56","slug":"bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives","status":"publish","type":"blog","link":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/","title":{"rendered":"Bad Data Migration: Common Cause for Problematic Go-lives"},"content":{"rendered":"<p>Are you facing challenges with your data migration process? Here are some thoughts from the Fortude Infor M3 experts.<\/p>\n<h6><strong>Plan Ahead <\/strong><\/h6>\n<ul>\n<li>Data Migration Planning should be a key project planning activity<\/li>\n<li>Identify the different data sources for the ERP up-front<\/li>\n<li>Nominate Owners for each piece of data<\/li>\n<li>Brief them thoroughly on the Cleansing &amp; Transformation requirements from source system to M3<\/li>\n<li>Assess the volumes of Master and Transactional data to be migrated and the time needed to extract and cleanse them<\/li>\n<li>Plan at least 2 trial data migrations<\/li>\n<li>Plan fall-back \/ contingency processes for each step<\/li>\n<li>Define Acceptance Criteria and owners for Signoff<\/li>\n<\/ul>\n<p><img decoding=\"async\" src=\"https:\/\/fortude.co\/wp-content\/uploads\/2017\/03\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1024x512-2.png\" alt=\"\" \/><\/p>\n<h6>Develop and Test your Migration Tools<\/h6>\n<ul>\n<li>Use actual data for your testing<\/li>\n<li>Consider Data Type conversions when migrating between different Operating Systems<\/li>\n<li>Load Test you migration tools and scripts<\/li>\n<li>Document the Data Migration Process and data mapping rules<\/li>\n<li>Automate the data transformation where large volumes of data are involved<\/li>\n<li>Time your data migrations to estimate the time needed for the Final Go Live<\/li>\n<li>Freeze your solution : revisit your data migration design if any configuration changes are done<\/li>\n<li>Develop custom templates if required for recording data during system blackout<\/li>\n<li>Clearly define Go-No-Go Criteria for final Go-Live<\/li>\n<\/ul>\n<h6> Execute your Data Migration According to the plan <\/h6>\n<ul>\n<li>Proactively reduce business transaction volume during the cutover period<\/li>\n<li>Differing of production \/ planning of deliveries outside of cutover period<\/li>\n<li>Ensure data accuracy through physical stock takes &amp; advance data cleansing<\/li>\n<li>Migrate Master Data in advance where possible<\/li>\n<li>Ensure sufficient hardware resources are allocated for the migration.<\/li>\n<li>Ensure timely and accurate communication between all stakeholders during the migration<\/li>\n<li>Escalate any exceptions and review Go-No-Go Criteria with all stakeholders<\/li>\n<li>Ensure users are allocated for entering \/ uploading backlogged (blackout period) transactions<\/li>\n<li>Freeze and Archive the Source and Migrated data<\/li>\n<\/ul>\n<p><em>Author: <\/em><br \/>\nNiranjan Vaidyakularatne<br \/>\nVice President \u2013 ERP Pre-Sales &amp; Innovation, Infor Services<\/p>\n","protected":false},"featured_media":14392,"template":"","meta":{"_acf_changed":false,"content-type":""},"industry":[],"service":[60],"class_list":["post-10264","blog","type-blog","status-publish","has-post-thumbnail","hentry"],"acf":{"blog_render_type":"legacy_acf","sections":[{"section_title":"Introduction","section_content":"<p>Are you facing challenges with your data migration process? Here are some thoughts from the Fortude Infor M3 experts.<\/p>","section_image":"","table_rows":null,"pro-tip":""},{"section_title":"Plan Ahead","section_content":"<ul><li>Data Migration Planning should be a key project planning activity<\/li><li>Identify the different data sources for the ERP up-front<\/li><li>Nominate Owners for each piece of data<\/li><li>Brief them thoroughly on the Cleansing &amp; Transformation requirements from source system to M3<\/li><li>Assess the volumes of Master and Transactional data to be migrated and the time needed to extract and cleanse them<\/li><li>Plan at least 2 trial data migrations<\/li><li>Plan fall-back \/ contingency processes for each step<\/li><li>Define Acceptance Criteria and owners for Signoff<\/li><\/ul>","section_image":14217,"table_rows":null,"pro-tip":""},{"section_title":"Develop and Test your Migration Tools","section_content":"<ul><li>Use actual data for your testing<\/li><li>Consider Data Type conversions when migrating between different Operating Systems<\/li><li>Load Test you migration tools and scripts<\/li><li>Document the Data Migration Process and data mapping rules<\/li><li>Automate the data transformation where large volumes of data are involved<\/li><li>Time your data migrations to estimate the time needed for the Final Go Live<\/li><li>Freeze your solution : revisit your data migration design if any configuration changes are done<\/li><li>Develop custom templates if required for recording data during system blackout<\/li><li>Clearly define Go-No-Go Criteria for final Go-Live<\/li><\/ul>","section_image":"","table_rows":null,"pro-tip":""},{"section_title":"Execute your Data Migration According to the plan","section_content":"<ul><li>Proactively reduce business transaction volume during the cutover period<\/li><li>Differing of production \/ planning of deliveries outside of cutover period<\/li><li>Ensure data accuracy through physical stock takes &amp; advance data cleansing<\/li><li>Migrate Master Data in advance where possible<\/li><li>Ensure sufficient hardware resources are allocated for the migration.<\/li><li>Ensure timely and accurate communication between all stakeholders during the migration<\/li><li>Escalate any exceptions and review Go-No-Go Criteria with all stakeholders<\/li><li>Ensure users are allocated for entering \/ uploading backlogged (blackout period) transactions<\/li><li>Freeze and Archive the Source and Migrated data<\/li><\/ul><em>Author: <\/em>\nNiranjan Vaidyakularatne\nVice President \u2013 ERP Pre-Sales &amp; Innovation, Infor Services","section_image":"","table_rows":null,"pro-tip":""}],"bottom_sections":null},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.7 (Yoast SEO v27.7) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Bad Data Migration: Common Cause for Problematic Go-lives<\/title>\n<meta name=\"description\" content=\"Expert insights on overcoming ERP data migration challenges, ensuring successful go-lives. Plan, assess and define your migration strategy.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Bad Data Migration: Common Cause for Problematic Go-lives\" \/>\n<meta property=\"og:description\" content=\"Expert insights on overcoming ERP data migration challenges, ensuring successful go-lives. Plan, assess and define your migration strategy.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/\" \/>\n<meta property=\"og:site_name\" content=\"Fortude\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-07T04:51:56+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/fortude.co\/wp-content\/uploads\/2017\/03\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/\",\"url\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/\",\"name\":\"Bad Data Migration: Common Cause for Problematic Go-lives\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/fortude.co\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/fortude.co\\\/wp-content\\\/uploads\\\/2017\\\/03\\\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png\",\"datePublished\":\"2017-03-24T07:45:25+00:00\",\"dateModified\":\"2026-05-07T04:51:56+00:00\",\"description\":\"Expert insights on overcoming ERP data migration challenges, ensuring successful go-lives. Plan, assess and define your migration strategy.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/#primaryimage\",\"url\":\"https:\\\/\\\/fortude.co\\\/wp-content\\\/uploads\\\/2017\\\/03\\\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png\",\"contentUrl\":\"https:\\\/\\\/fortude.co\\\/wp-content\\\/uploads\\\/2017\\\/03\\\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png\",\"width\":2108,\"height\":1054},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/fortude.co\\\/blog\\\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/fortude.co\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Bad Data Migration: Common Cause for Problematic Go-lives\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/fortude.co\\\/#website\",\"url\":\"https:\\\/\\\/fortude.co\\\/\",\"name\":\"Fortude\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/fortude.co\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/fortude.co\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/fortude.co\\\/#organization\",\"name\":\"Fortude\",\"url\":\"https:\\\/\\\/fortude.co\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/fortude.co\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/fortude.co\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Fortude-Logo.svg\",\"contentUrl\":\"https:\\\/\\\/fortude.co\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Fortude-Logo.svg\",\"width\":100,\"height\":15,\"caption\":\"Fortude\"},\"image\":{\"@id\":\"https:\\\/\\\/fortude.co\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Bad Data Migration: Common Cause for Problematic Go-lives","description":"Expert insights on overcoming ERP data migration challenges, ensuring successful go-lives. Plan, assess and define your migration strategy.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/","og_locale":"en_GB","og_type":"article","og_title":"Bad Data Migration: Common Cause for Problematic Go-lives","og_description":"Expert insights on overcoming ERP data migration challenges, ensuring successful go-lives. Plan, assess and define your migration strategy.","og_url":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/","og_site_name":"Fortude","article_modified_time":"2026-05-07T04:51:56+00:00","twitter_card":"summary_large_image","twitter_image":"https:\/\/fortude.co\/wp-content\/uploads\/2017\/03\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/","url":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/","name":"Bad Data Migration: Common Cause for Problematic Go-lives","isPartOf":{"@id":"https:\/\/fortude.co\/#website"},"primaryImageOfPage":{"@id":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/#primaryimage"},"image":{"@id":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/#primaryimage"},"thumbnailUrl":"https:\/\/fortude.co\/wp-content\/uploads\/2017\/03\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png","datePublished":"2017-03-24T07:45:25+00:00","dateModified":"2026-05-07T04:51:56+00:00","description":"Expert insights on overcoming ERP data migration challenges, ensuring successful go-lives. Plan, assess and define your migration strategy.","breadcrumb":{"@id":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/#primaryimage","url":"https:\/\/fortude.co\/wp-content\/uploads\/2017\/03\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png","contentUrl":"https:\/\/fortude.co\/wp-content\/uploads\/2017\/03\/Mitigate_Risks_of_Bad_Data_Migration_of_Your_M3_Rollout-24-Mar-2017-01.-1.png","width":2108,"height":1054},{"@type":"BreadcrumbList","@id":"https:\/\/fortude.co\/blog\/bad-data-migration-is-a-common-cause-for-failed-or-problematic-erp-go-lives\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/fortude.co\/"},{"@type":"ListItem","position":2,"name":"Bad Data Migration: Common Cause for Problematic Go-lives"}]},{"@type":"WebSite","@id":"https:\/\/fortude.co\/#website","url":"https:\/\/fortude.co\/","name":"Fortude","description":"","publisher":{"@id":"https:\/\/fortude.co\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fortude.co\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/fortude.co\/#organization","name":"Fortude","url":"https:\/\/fortude.co\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/fortude.co\/#\/schema\/logo\/image\/","url":"https:\/\/fortude.co\/wp-content\/uploads\/2026\/02\/Fortude-Logo.svg","contentUrl":"https:\/\/fortude.co\/wp-content\/uploads\/2026\/02\/Fortude-Logo.svg","width":100,"height":15,"caption":"Fortude"},"image":{"@id":"https:\/\/fortude.co\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/blog\/10264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/types\/blog"}],"version-history":[{"count":0,"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/blog\/10264\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/media\/14392"}],"wp:attachment":[{"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/media?parent=10264"}],"wp:term":[{"taxonomy":"industry","embeddable":true,"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/industry?post=10264"},{"taxonomy":"service","embeddable":true,"href":"https:\/\/fortude.co\/wp-json\/wp\/v2\/service?post=10264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}