Small and medium business | Business Central, N...

Data Migration

(6) Share

Report

Posted on by CU23070820-0

Hello everyone,

I’m looking for guidance on best practices for data migration in Microsoft Dynamics 365 Business Central where a company is standardizing its Chart of Accounts (COA) during implementation.

Scenario:

A group company has multiple subsidiaries, each currently operating with different COA structures.
As part of the migration to Business Central, the group has decided to introduce a new standardized COA that will be used across all subsidiaries.
- Historical data exists under the old COA structures, which do not fully align with the new standardized COA.

Questions:

What is the recommended approach to migrate opening balances and historical transactional data when the COA structure has changed?
Is it better practice to:
- Map old G/L accounts to the new standardized COA during migration, or
- Migrate only opening balances and keep historical data outside Business Central (e.g., legacy system or data warehouse)?

How do consultants typically handle comparative reporting (prior-year figures) when COA structures differ?

Are there standard tools, templates, or methodologies within Business Central (or common partner practices) that help manage COA re-mapping during migration? Any insights, real-world experiences, or recommended approaches would be greatly appreciated.

Thank you in advance for your support.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

YUN ZHU 98,242 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

In this situation, we would typically use the Financial Reports feature to create the new standardized COA instead of rebuilding the branch office's COA. While retaining the opening balance is possible, preserving historical data would require reposting all previous data with the current posting group settings, which is virtually impossible.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,876 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

It is good approach that client isoving forward with common COA accross multiple entities.

To give answers.

It is not advisable to move historical balances, as then you have to map all the old g/l to new g/l for all the past data and its too much. Only upload opening balances with new g/l codes.

As regarding comparitive reporting it is most of the time outside system however if you do need it from system, you can create a custom field in g/l called old g/l code, from there then you can create new comparative reports. Not advisable to compare the old reports with new reports as such. Better to convert old reports with the mapping and then compare it with new reports. Its better to create static old reports with new g/l mappings.

As regards to tool, as such there is no tool in Business central to support that but excel if the best way to do the remapping.

However in past we did maintained a table for mapping in new system for reference purpose. So in future if i have to build a report from new data but in old g/l format it becomes easier.

I hope this helps.

Regards,

Dhiren.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 11,394 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

Best practice when standardizing a COA during a BC implementation is to migrate only opening balances mapped to the new standardized COA and keep detailed historical transactions in the legacy system or a reporting layer. Mapping full transactional history across different COAs is high risk, costly, and rarely audit-friendly, while auditors are generally fine with BC being the system of record from go-live forward. Opening balances are typically aggregated in the legacy system, mapped via an Excel-based COA mapping table, and posted into BC using opening balance journals. For comparative or prior-year reporting, consultants usually rely on Power BI or Excel, combining legacy historical data with BC current data, rather than forcing mismatched history into BC. There’s no standard Microsoft tool for automatic COA re-mapping—this is always a controlled finance-led design exercise.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 21,573 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Best practice is to migrate only opening balances mapped to the new standardized COA and keep historical transactions outside Business Central. Comparative reporting is handled via legacy systems or BI tools. Full historical migration with changed COA is rarely recommended.

Was this reply helpful? Yes No