What Data Moves to Business Central?
The migration scope depends on the dealership's current Hedberg configuration, reporting requirements, and the capabilities of the target Business Central environment. Teams should classify records as master data, open transactions, historical records, or configuration settings before transferring them.
- Financial data: General ledger balances, open customer invoices, vendor liabilities, deposits, credits, and outstanding payments.
- Customer and vendor records: Account identifiers, contact details, payment terms, credit settings, and relevant tax information.
- Inventory and purchasing: Item codes, warehouse quantities, costs, purchase orders, receipts, and outstanding supplier commitments.
- Sales and projects: Open sales orders, order lines, delivery details, installation commitments, and customer-specific pricing where supported.
- Historical information: Selected invoices, transaction histories, and reports required for audits, customer service, and trend analysis.
Each category needs a defined destination, transformation rule, and reconciliation method. For example, a Hedberg item identifier may need to map to a Business Central item number, while customer deposits must retain the correct customer reference and accounting treatment.
How the Migration Process Works
The project begins with discovery. Finance, purchasing, inventory, sales, and IT stakeholders identify which records must move, which processes will change, and which historical records should remain accessible through archived reports. A clear scope helps teams define acceptance criteria before data is transferred.
Next, teams profile and cleanse the source data. They identify duplicate customer records, inactive item codes, missing vendor details, inconsistent units of measure, and balances that need investigation. Mapping documents then connect Hedberg fields to Business Central fields, including transformations for dates, currencies, posting groups, tax categories, and dimensions.
The migration team loads representative data into a test environment and validates the results. Testing should cover complete business scenarios, such as receiving a supplier shipment, invoicing a customer, applying a payment, and posting a general ledger entry. After issues are resolved, the team rehearses the final migration, confirms cutover responsibilities, and establishes a process for handling transactions created during the transition.
This is a practical example of System Migration: moving business operations and information between systems while managing dependencies, continuity, and validation. The broader ERP design also matters. Understanding How Many Levels Does a Typical ERP System Include? can help stakeholders distinguish infrastructure and data services from business applications and the finance workflows built around them.
Financial Reconciliation and Data Integrity
Finance should validate the migrated opening position before users rely on Business Central for live reporting. The general ledger trial balance should agree with the approved source balances after accounting adjustments. Accounts receivable and accounts payable control accounts should reconcile to their respective open-item details, while inventory quantities and values should agree with the signed-off inventory records.
Teams should also check that customer deposits, credit notes, unapplied receipts, and outstanding vendor invoices retain their correct status. A transaction count alone is not sufficient: a migration can transfer every row while still assigning the wrong account, currency, posting group, or customer reference.
For international transactions, confirm how exchange-rate data will be maintained and applied. Central Bank Exchange Rates are reference rates published by central banks and can support currency-related analysis when appropriate to the company's accounting policy. The target configuration must still follow the business's approved exchange-rate sources and posting rules.
Integrating Business Central with Finance Workflows
Business Central provides the ERP environment, but finance processes may also depend on document capture, approval routing, payment preparation, and exception handling. The design should define which tasks stay within the ERP and which connect through approved integrations. How ERP and Business Processes Work Together is a useful lens for ensuring that system configuration supports the actual sequence of business activities rather than merely reproducing old screens.
When extending finance processes, teams can use a Flexible Workflow to route accrual approvals according to policy, business unit, department, or approval thresholds. Vendor payment planning can incorporate Late Payment Recommendations to help prioritize payments, manage due dates, and support cash flow planning. Industry-specific finance rules may also be configured through the Hyperbots Platform, including contextual tax validation and workflow rules where these capabilities fit the approved architecture.
For purchasing, validate requisition approvals, supplier commitments, and the relationship between each purchase order, receipt, and vendor invoice. An ERP Automation Guide: Modules & Playbooks can help teams identify which finance and procurement activities are suitable for integration after the core ERP data has been validated.
Cutover Planning and Ongoing Controls
Before go-live, assign owners for final data extraction, transformation, loading, reconciliation, and business approval. Agree on a transaction freeze or controlled handover window, document how late-arriving transactions will be handled, and retain migration logs for traceability. Users should receive role-based training for the Business Central processes they will perform.
After go-live, monitor posting errors, unreconciled balances, duplicate records, inventory discrepancies, and delays in processing orders or invoices. Establish a clear support route so users can report incorrect mappings or unexpected results. Review reports and access permissions regularly as the dealership refines its operating model.
For multi-entity organizations, Central Finance describes an approach to bringing financial information and selected finance processes together across entities. It is a related consideration when planning consolidated reporting, but it is not a substitute for correctly configuring Business Central company structures, currencies, and posting rules.
Summary
Hedberg to Business Central Migration transfers dealership data and workflows into Microsoft Dynamics 365 Business Central through structured discovery, data mapping, testing, reconciliation, and controlled cutover. The strongest results come from clearly defined migration scope, accurate financial opening balances, validated inventory and open transactions, and workflows aligned with the new ERP. Treat migration as a business-control initiative, not simply a data transfer, and use the Central Finance concept where relevant to broader multi-entity planning.