Dynamics GP to Business Central Migration
Move from Dynamics GP without losing control of the business logic around it.
Plan the transition to Dynamics 365 Business Central around the data, customizations, integrations and finance controls that must remain correct before, during and after cutover.
- Understand Dynamics GPData, logic and dependencies
- Control the transitionReadiness, trial loads and reconciliation
- Accept Business CentralVerified process and operating state
A defined first step
Start with a GP-to-Business-Central readiness assessment.
Bring the GP modules, extensions, integrations, data history and finance requirements that the next system must support.
Agree a review of process fit, customization dependencies and migration controls. The proposed output is a readiness and gap summary, reconciliation requirements and a phased transition scope.
Scope, access, deliverables, fees and timing are agreed before work begins. Remote delivery arrangements include working-hour overlap, review points and named decision owners.
Discuss the assessment scopeBringing us into an existing consultancy engagement? Review specialist delivery for ERP consultancies.
The decision in front of you
A platform transition becomes a business-continuity decision.
The difficult part is not creating an empty target. It is deciding what the current environment means and proving what must work next.
- The current Dynamics GP environment no longer fits the organization’s platform or operating direction.
- Years of customizations and reporting logic make the real migration scope difficult to see.
- Finance needs a defensible decision about what history to migrate, retain or archive.
- Connected systems and manual workarounds could fail if they are treated as late cutover tasks.
Readiness first
Understand the source before committing to the migration shape.
Source reality
Inventory GP companies, modules, data history, customizations, reports, integrations and operating dependencies before defining the target.
Target process fit
Decide where Business Central configuration fits, where an AL extension is justified and where the process itself should change.
Transition boundary
Define data scope, interface cutover, coexistence, ownership and acceptance so the migration is more than a technical load.
Dynamics GP module coverage
Inventory the GP modules and controls the transition must account for.
Financial management
Stabilize the accounting core and preserve the meaning behind existing controls.
- General Ledger, Payables, Receivables, Bank Reconciliation and Fixed Assets
- Multicurrency, Analytical Accounting, Cash Flow, deferrals and period-end processing
- Multi-company, intercompany and multi-entity behavior
- Posting setup, batches, distributions, subledger reconciliation and audit support
Sales, purchasing and inventory
Resolve transaction and inventory issues across connected distribution processes.
- Sales Order Processing, Purchase Order Processing and Inventory Control
- Pricing, allocations, fulfillment, returns, landed-cost dependencies and item tracking
- Inventory costing, historical transactions, valuation, adjustments and reconciliation
- Order-to-cash and procure-to-pay integrations, including EDI and commerce channels
Manufacturing, projects and service
Support operational modules and adjacent products that often contain critical business logic.
- Manufacturing bills, routings, planning, production, costing and variance analysis
- Project Accounting, time, expense, billing, revenue recognition and profitability
- Field Service, service calls, contracts, equipment, parts, technicians and depot processes
- Industry or ISV extensions whose data and rules must be understood before change
Troubleshooting and stabilization
Find the cause across application, SQL, integrations and operating practice.
- Posting interruptions, stuck batches, reconcile/check-links findings and data inconsistencies
- Performance, blocking, SQL jobs, maintenance, environment health and upgrade readiness
- Security, dictionaries, forms, reports, client/runtime issues and repeatable diagnostics
- Incident containment, root-cause analysis, safe correction and prevention runbooks
Customization and integration recovery
Take ownership of inherited logic before modifying or replacing it.
- Dexterity dictionaries, Modifier/VBA, Visual Studio Tools and .NET utilities
- eConnect, Web Services, Integration Manager, SmartConnect, Scribe and file/EDI interfaces
- SQL procedures, views, triggers, staging, Windows services, schedulers and monitoring
- Source recovery, dependency mapping, error handling, reconciliation and support handoff
Modernization and migration readiness
Improve GP where it remains valuable and prepare evidence for a later platform decision.
- Version, infrastructure and SQL assessment; upgrade and server-migration planning
- Company, module, customization, report, integration and data-history inventories
- Replace, retain, redesign or retire decisions for each material dependency
- Business Central fit-gap, data scope, trial migration, reconciliation and cutover planning
Development and integration tools
Trace GP tools, code and interfaces before redesigning them.
GP development stack
Recover and maintain the toolchain appropriate to each customization.
- Dexterity, Modifier with VBA and Visual Studio Tools for .NET
- eConnect, Dynamics GP Web Services, Integration Manager, Extender and Power Tools
- Dictionaries, forms, reports, chunk deployment, source control and build documentation
SQL and data engineering
Use supported application behavior with disciplined SQL diagnostics and controlled data work.
- SQL Server diagnostics, query tuning, blocking, jobs, backups and environment checks
- Read-only analysis, controlled staging, data repair plans, migration extracts and reconciliation
- Schema and dependency discovery across company and system databases
Reporting and analytics
Preserve operational and financial reporting while reducing hidden logic.
- SmartList and SmartList Builder, Report Writer, SSRS and Excel reports
- Power BI, Jet Reports, Solver and controlled warehouse or lake feeds
- Inventory valuation, financial statements, exception reporting and reconciled extracts
Integration operations
Make legacy and modern connections observable and recoverable.
- SmartConnect, Scribe, eConnect, .NET services, APIs, SQL staging, files and EDI
- Batch scheduling, logging, alerting, retry, duplicate control and reconciliation
- CRM, AP automation, treasury, tax, payroll, commerce and document-system interfaces
Representative product ecosystem
Assess connected products before setting the cutover scope.
Examples identify commonly encountered products and categories; they do not imply vendor partnership or endorsement.
Integration and data movement
Examples include eOne SmartConnect and Popdock, Scribe, Integration Manager and controlled custom services.
Multi-entity and intercompany
Examples include Binary Stream Multi-Entity Management, Nolan products and purpose-built intercompany logic.
Payments, treasury, tax and payroll
Examples include Mekorma, Tipalti, HighRadius, Avalara, Greenshades and bank-specific formats.
Service and industry solutions
Examples include WennSoft and other field-service, construction, rental or industry products.
EDI and commerce
Examples include TrueCommerce, SPS Commerce, Shopify, BigCommerce, Magento and marketplace connectors.
Reporting and close
Examples include SSRS, SmartList, Power BI, Jet, Solver, BlackLine and document-management platforms.
Transition controls
Make data, customization and integration decisions explicit.
Data scope and meaning
Agree what moves, how business meaning maps to the target and how retained history remains accessible.
Customization disposition
Classify each customization as replace, redesign, retire or rebuild—without carrying old complexity forward by default.
Integration transition
Map every connected flow, update its contract and prove failure handling, ownership and reconciliation before cutover.
Financial acceptance
Use agreed control totals, representative transactions and exception records to make acceptance explicit.
Controlled migration method
Rehearse, reconcile and accept before cutover.
Discover
Establish the current GP, data, customization, process and integration baseline.
Decide
Confirm target-process fit and document the disposition of each material dependency.
Map
Translate data and business rules into controlled target definitions and acceptance criteria.
Rehearse
Run trial migrations and exercise representative processes, integrations and exception paths.
Reconcile
Compare source and target control totals, investigate differences and retain evidence.
Cut over
Execute an owned transition with entry criteria, checkpoints and a documented recovery decision.
Decision and delivery evidence
Leave each phase with reviewable migration outputs.
- Migration readiness findings and dependency inventory
- Customization, report and integration disposition record
- Data scope, mapping, trial-load and reconciliation plan
- Business-process validation and acceptance evidence
- Cutover runbook, ownership map and recovery criteria
Common questions
Clarify scope before deciding on a solution.
Can you support Dynamics GP without forcing an immediate migration?
Yes. Stabilization, upgrades, integrations, reporting, controls and inherited customizations can be addressed while a platform decision remains open.
What makes the work techno-functional?
The diagnosis connects finance and operational intent to GP module behavior, SQL data, custom code, integrations, reports and support procedures.
Can inherited Dexterity, VBA or .NET customizations be recovered?
They can be inventoried, reproduced, source-assessed and dependency-mapped, then stabilized, documented, replaced, redesigned or retired.
Can you diagnose third-party product and integration failures?
Yes, when access and licensing permit. The review follows the transaction across GP, the product, SQL, files or APIs, schedules, logs and reconciliation points.
How do we know whether we are ready for Business Central?
Readiness requires current processes, data quality, customizations, reports, integrations, controls, history requirements, ownership and target fit to be explicit.
Do you rebuild every GP customization in Business Central?
No. Each dependency is classified as standard capability, supported extension, process redesign, focused rebuild, coexistence or retirement.
Next step
Discuss your GP-to-Business Central migration
Describe the current GP environment, the target decision and the risks that need to be understood first.