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

Data Migration if cutover date is in between the year

(2) Share

Report

Posted on by CU04081252-0

Hi Experts,

We have a client with a planned Go-Live on 1st May, and we are currently in the process of planning the data migration strategy from 1st January onwards.

We would like guidance on the most appropriate approach for this scenario:

Should we migrate only opening balances as of 30th April, or should we also consider migrating detailed transactions (Jan–Apr)?
If transactions are to be migrated, what would be the recommended approach for the following:
- Purchase Orders
- Purchase Invoices
- Sales Invoices
- General Ledger transactions
- Item/Inventory balances
In case of transaction-level migration:
- How should the data be uploaded in Business Central (recommended sequence and tools)?
- How can we ensure proper reconciliation between legacy system and Business Central?
Specifically for inventory:
- How should inventory balances (quantity and value) be brought into the system?
- How should additional costs (freight, charges, adjustments) be handled during migration?
What is the recommended approach for:
- Open vs closed transactions
- Ensuring accurate AR/AP aging
- Matching trial balance and subledgers (GL vs Customer/Vendor vs Inventory)

From our understanding, one common approach is to migrate:

Master data
Opening balances
Open transactions (AR/AP/PO/SO)
while keeping historical closed transactions in the legacy system, as full historical migration can be complex and time-consuming ()

However, we would like to understand:

In which scenarios detailed transaction migration (Jan–Apr) is recommended
And how to execute it correctly without reconciliation issues

It would be very helpful if someone could share a detailed, practical approach or real-life implementation experience, including examples or best practices followed during similar go-live scenarios.

Thanks in advance!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

RockwithNav 9,156 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Should we migrate only opening balances as of 30th April, or should we also consider migrating detailed transactions (Jan–Apr)?

Typically, when implementing a new system, it’s best to start with opening balances rather than bringing in extensive historical transactions. There have been cases where clients prefer to migrate detailed transactions for a specific period (like your case., January to April). While this is possible, it’s important to understand that detailed data migration comes with additional validations and complexities. If you are only migrating detailed GL entries, it generally requires fewer precautions. However, migrating detailed payables and receivables is more complex, as it requires all application entries to be carried over. This ensures that invoices that are already closed remain properly closed in the new system with correct applied entries. Overall, this portion can be a time-consuming.

If transactions are to be migrated, what would be the recommended approach for the following:

Purchase Orders - Configuration Package

Purchase Invoices - Process OR Import from Config Package(Open PO) and than Post.

Sales Invoices - Process OR Import from Config Package(Open SO) and than Post.

General Ledger transactions - General Journal

Item/Inventory balances - Item Journal

If using Bank then use General Journal to load the Banks opening Balance.

In case of transaction-level migration:

How should the data be uploaded in Business Central (recommended sequence and tools)?

Open - Configuration Package.

Closed - Custom Process / Import the posted one as open from configuration package and then post. See which ever is easier for you.

How can we ensure proper reconciliation between legacy system and Business Central?

Once the data is loaded - Run GL Trial, Customer Trial, Vendor Trial, Inventory Valuation and Bank trial to make sure they are in lined with the old system.

Specifically for inventory:

How should inventory balances (quantity and value) be brought into the system?

Item Journal/ Warehouse Item Journal. This depends what Location configuration are you using Normal/Advanced Warehouse.

How should additional costs (freight, charges, adjustments) be handled during migration?

If you have decided to bring all posted invoice transactions into the system then you need top take care of these at that time only. So if you importing PO and then willing to post it then add Item Charge in the Lines or GL account for any expense and then execute posting. If you are writing a process then add these the same way.

What is the recommended approach for:

Open vs closed transactions

Open - Configuration Package

Closed - Process, this will need quality efforts as you need to take care of all the application's.

Ensuring accurate AR/AP aging

Once you load the GL Balance and are done with the Customers and Vendors balances which are subledgers then you can first reconcile these making sure that AP AR is perfectly tying up with the GL. Post this you can run AR AP aging Reports and match with the old system

Matching trial balance and subledgers (GL vs Customer/Vendor vs Inventory)

Once you load the GL balances, customer balances, vendor balances, and the item master with inventory counts, you can run reconciliation reports to ensure everything ties correctly. Your Receivables account should match the total customer balances, and your Payables account should match the total vendor balances. Similarly, the inventory valuation should align with the inventory account once everything is loaded and completed. Also, review how many Receivables, Payables, and Inventory accounts you are using in your setup.

From our understanding, one common approach is to migrate:

Master data

Opening balances

Open transactions (AR/AP/PO/SO)
while keeping historical closed transactions in the legacy system, as full historical migration can be complex and time-consuming ()

This is 100% true and in lined.

In which scenarios detailed transaction migration (Jan–Apr) is recommended

This largely depends on how reluctant the customer is. The general recommendation is not to bring in detailed historical data. However, if you are migrating data within the current financial year, the customer may request to include detailed transactions. This is a valid request, as they may want the current financial year data to remain fully detailed and intact.

And how to execute it correctly without reconciliation issues

Guess I answered this above.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,600 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I always recommend importing only opening balances. If you want to import transaction data, you must import it in advance, especially partially posted data, because this is related to inventory and financial data.

Hope this can give you some hints.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 16,916 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

For a 1 May go-live, I’d keep it simple: migrate master data, opening balances, and open transactions only (open AR/AP and usually open PO/SO if needed operationally), and leave closed Jan–Apr history in the legacy system, because that is the lowest-risk option and the easiest to reconcile; detailed Jan–Apr transaction migration is only worth doing if the client has a real business need for historical drilldown inside BC, and then it should be done very carefully with repeated dry runs. Typical order is setup/master data first, then inventory opening balances, then customer/vendor open entries, then open documents, then final G/L opening balances/reconciliation, using configuration packages / Excel / migration tools depending on the source system. For inventory, bring in opening quantity and value, not every old cost layer unless history is required, and make sure the final result ties to the inventory valuation and G/L. The big goal is simple: AR aging, AP aging, inventory valuation, and trial balance must all match at cutover.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Gerardo Rentería Ga... 27,052 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

How to Create Opening Balances in the G/L in Business Central - Dynamics Power Play

Search Results for “opening”

Best Regards
Gerardo

Was this reply helpful? Yes No