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

Opening balances for Projects in BC when migrating from legacy system

(3) Share

Report

Posted on by October Sky

711

When migrating from a legacy system to Business central, it is quite difficult to create opening balances for Projects/Jobs that are in progress, i.e. that cannot be finished before the migration occurs. Has anyone susggested methodologies for migrating opening Project balances, especially WIP and continuing in a stabilising manner post migration on the same project. All Project costs need to be kept together from the legacy system and placed on BC for the same project. Some long term projects exist; hence this requirement. The same with outstanding invoices.

Categories:

Dynamics 365 Business Central

Dynamics 365 Business Central migration

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

AndrewThomas81 2,306 on at

Like (1)

Report
Copy link

Link copied!

Ultimately you will need to post the required entries to reconcile to the balance from the other system.

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn

Was this reply helpful? Yes No
Suggested answer

Teagen Boll 3,452 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi, a lot of clients I work with take one of two approaches:

1. Work in parallel and complete projects in the old system and just bring in GL balances as they are completed. Simple, easy but a bit manual and if you have a lot of projects it can be a hard sell.

2. Setup the projects as if they have zero work done. Then use the Project Journal to post project subledger only transactions as of the cutover date to load in the appropriate costs. This can lead to errors but the idea is for costs you would have just the subledger entries and for the billable invoices you create they would need to be a net zero dollar GL impact. On your invoice lines you would just set the line as the same as the receivables account (or temporarily change your receivables account for those customers). I've taken this approach before but you typically want to create backups and test so it can add some time.

Best,

Teagen Boll, CPA

Work: Catapult ERP

Social: LinkedIn

Was this reply helpful? Yes No
Suggested answer

RockwithNav 9,225 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

You should be creating the Projects, Tasks, Planning lines and go with the Actual Cost.

WIP part let system calculate, I wont be suggesting to migrate anything.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 102,590 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

You can only do this by first importing the projects into BC and then posting them from BC.

You must confirm that the amount posted is consistent with the original system.

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 18,491 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

For in-progress Projects/Jobs, I normally avoid trying to recreate full legacy history unless the client really needs it inside BC. The cleaner method is to create the same Project + Project Tasks, post a summarized opening Project Journal by task/cost type/resource/item/G/L as of the cutover date, and separately migrate open customer invoices/AR as open documents or opening customer entries. For WIP, don’t just post random G/L balances if you still need BC to continue calculating WIP on the same project; first agree the cutover position, load the project costs/billable values in a way BC can read through project ledger entries, then run Project Calculate WIP and Project Post WIP to G/L from BC going forward. For long-term projects, keep the legacy detail in an archive/report and bring only summarized but auditable opening project entries into BC, otherwise reconciliation and WIP can become very messy.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,872 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

this is a classic pain and there is no clean Job opening balance like there is for G/L, you have to rebuild the project history with Job Journal entries so the WIP and the cost continue right. What I seen work is bring each in progress project in as summarised Job Ledger Entries, group the legacy cost by the things you care about going forward, by Job Task and by type, item, resource, G/L, rather than line by line, otherwise you drown. Enough granularity to keep reporting honest, not the whole legacy detail.

Key point, post those opening entries through the Job Journal so they hit the Job Ledger, then run WIP calculation in BC so the WIP matches what you carried over. If you just drop a G/L balance the project itself stays empty and WIP recognition breaks later. So the project ledger and the G/L both need to agree at cutover, that reconciliation is the real work.
Outstanding invoices are separate, those come in through the normal customer and vendor opening balances, not the Job, but you link them back to the project with the Job fields so future billing and WIP see them.

Are these fixed price or cost plus projects, because the WIP method changes how you seed the opening figures? And how much legacy detail do you actually need to keep visible on the project after go live?

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

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

Like (2)

Report
Copy link

Link copied!

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

Solved: Business Central Jobs Beginning Balances import for Project Jobs

Walkthrough - Calculating work in process for a project - Business Central | Microsoft Learn

Best Regards
Gerardo

Was this reply helpful? Yes No