{"title":"Validate Dynamics GP data migration","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/migrate-gp-validation/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-gp-validation, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-gp-validation","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Validate Dynamics GP data migrated to Business Central, review failed tests and record details, and configure automatic or manual validation.","date":"2026-11-17","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Validate Dynamics GP data migration","slug":"validate-dynamics-gp-data-migration","at":0,"chars":5229},{"level":2,"title":"How validation works","slug":"how-validation-works","at":507,"chars":790},{"level":2,"title":"Run migration validation","slug":"run-migration-validation","at":1297,"chars":1739},{"level":3,"title":"Automatic validation","slug":"automatic-validation","at":1400,"chars":830},{"level":3,"title":"Manual validation","slug":"manual-validation","at":2230,"chars":806},{"level":2,"title":"View validation results","slug":"view-validation-results","at":3036,"chars":971},{"level":2,"title":"Manage validation tests","slug":"manage-validation-tests","at":4007,"chars":553},{"level":2,"title":"Entities checked during validation","slug":"entities-checked-during-validation","at":4560,"chars":573},{"level":2,"title":"Related information","slug":"related-information","at":5133,"chars":96}],"text":"# Validate Dynamics GP data migration\nThe migration validation feature checks data migrated from Dynamics GP to Business Central by comparing replicated GP source data with migrated data in Business Central. This validation process helps you identify discrepancies between the two sets of data.\nThe feature can run automatically as part of the data upgrade or be triggered manually after migration. It tests multiple entities, including G/L accounts, customers, vendors, items, and other key business data.\n## How validation works\nMigration validation compares specific data points between the replicated Dynamics GP source data and the migrated data in Business Central. For each entity tested, the validation process checks whether values match expected results based on the source data.\nWhen validation completes, you can view a summary that shows:\n Entities that were tested\n Description of each validation test performed\n Number of records that failed validation for each test\n Detailed information about specific records that didn't match\nThis information helps you identify and resolve data migration issues before you begin using Business Central. Validation checks specific data points, not every field or transaction, so also review the migrated data against your business requirements.\n## Run migration validation\nYou can run validation in two ways depending on your workflow preferences:\n### Automatic validation\nBefore starting your migration, open Cloud Migration Management and select Configure GP Migration. On the GP Company Migration Configuration page, select Migration settings to open GP Migration Settings. In the Automatic Validation group, turn on GP. This option is on by default for a new migration configuration.\nWhen enabled, validation runs during the data upgrade without requiring manual intervention. In US environments, GP-US (1099) controls automatic validation of vendor 1099 information separately.\nThe Validation Errors Should Fail Migration group controls whether validation errors cause the data upgrade to fail. The options in this group are off by default. Review the recovery requirements before enabling them. See Upgrade data for Dynamics GP cloud migration<migration-data-upgrade-gp>.\n### Manual validation\nRun validation manually after migration by using either of these methods:\n On Cloud Migration Management, select Validation Errors in the Company Status FactBox, select Company Migration Status, and then choose Run All Validation.\n From Cloud Migration Management, select Validation Status, and then choose Run All Validation.\nThe action asks whether to force validation on all companies, including companies that were already validated. Choose Yes to retest those companies. This choice deletes their previous validation results before scheduling validation again. Choose No to validate only companies that haven't been validated.\nManual validation is useful when you want to retest data after making corrections or when you completed migration without automatic validation enabled.\n## View validation results\nAccess validation results from the Cloud Migration Management page. In the Company Status FactBox, Validation Errors displays the number of validation issues detected across all migrated companies.\nWhen you select Validation Errors, the Migration Validation Results page opens with a summary view showing:\n All entities that were tested\n Specific validation test descriptions\n Count of records that failed each test\nThe page hides passing tests by default. Turn off Hide passing tests to include tests with no reported failures.\nFor detailed investigation, select a test's Fail Count to open Migration Validation Errors and view:\n The entity and record identifier\n Company where the issue occurred\n Expected value from the source GP system\n Actual value found in Business Central after migration\nThis detailed view helps you investigate why validation failed for specific records. Expected and actual values can be redacted for sensitive data.\n## Manage validation tests\nYou can suppress failure logging for individual validation tests. If a specific validation test isn't relevant to your business requirements or you verified the data through other means, you can ignore its failures in future validation runs.\nTo ignore a validation test's failures, open the Migration Validation Results page, locate the test, and select Ignore. The test still runs, but it doesn't log new validation failures until you clear Ignore. This setting applies across companies and doesn't remove existing failures.\n## Entities checked during validation\nThe migration validation feature tests the following entities, depending on the modules and data selected for migration:\n G/L accounts\n Statistical accounts\n Bank accounts\n Customers and ship-to addresses\n Items\n Purchase orders and lines\n Vendors, order addresses, and remit-to addresses\n Vendor 1099 information in US environments\nEach entity has specific validation tests that check data points relevant to that business object. Some balance discrepancies are reported as warnings when migrated journal batches haven't been posted.\n## Related information\nDynamics GP data migrated to Business Central online<migrate-dynamics-gp>"}