Moving from Dynamics SL to Business Central: a migration for project-driven companies

Why firms start a Dynamics SL to Business Central migration

Dynamics SL is a Microsoft product that is no longer sold to new customers. Its development has wound down to maintenance. It still runs, but on servers you must maintain. New features such as Copilot, Power Automate flows and built-in Power BI land in Business Central instead.

Microsoft positions Business Central as the successor for SL customers in the small and midsize range. You get a web-based system that updates for you. The cycle of server upgrades, remote desktop access and custom code that only one person understands ends. Reports get better too.

Project accounting after a Dynamics SL to Business Central migration

SL customers usually care most about projects. In Business Central, a project has tasks and planning lines. You post usage and sales through project journals and documents. You work out work in progress with a method you choose. Resources carry cost and price, and time sheets feed usage with approval.

The models are close but not identical. SL's account categories, allocation methods and billing rules need care. They become project posting groups, task structures and invoicing steps. We prototype one real project from end to end in a sandbox. So project managers can judge the result early.

Subaccounts, segments and dimensions in the SL move

SL builds the posting key from an account plus a segmented subaccount. Business Central uses a natural account with dimensions on each entry. We take each subaccount segment, such as division, department or region. Then we turn it into a dimension with its own list of values.

Two of those become global dimensions that appear on every ledger page and filter. The rest are shortcut dimensions. Default dimensions and allowed combinations then enforce what the SL subaccount check used to enforce. So the system stops miscoded postings at entry, and they do not surface at month end.

Tooling for a Dynamics SL to Business Central migration

Microsoft's cloud migration tooling in Business Central includes a path for Dynamics SL. It can bring master records and open balances from a supported SL database. We check what it covers for your version and modules. Then we fill the gaps with configuration packages and journals.

Whichever route carries the data, the proof is the same. After a rehearsal run in a sandbox, your controller ties the trial balance, open receivables, open payables and project balances back to SL reports for the same date. The controller signs off before you set a cutover date.

Custom code, reports and payroll

SL screens changed with Customization Manager or VB tools do not transfer. We check each change against standard Business Central. Then we rebuild the ones you still need as AL extensions. We replace Crystal and FRx style reports with financial reports, Excel layouts and Power BI.

Business Central does not include US payroll. So SL payroll users move to a payroll provider that posts journals into the ledger. We plan that change alongside the ERP move. That includes how labor cost reaches projects. So the first pay run after cutover is not a surprise.

Dynamics SL to Business Central migration: common questions

Is Business Central the official replacement for Dynamics SL?

Microsoft points SL customers toward Business Central as the forward path and provides migration tooling for it. It is a different product, though. So the move is a new setup with a data load. Project-heavy firms should confirm that the project features fit before they commit.

Do SL licenses count toward Business Central?

Microsoft has run transition offers for customers on its older Dynamics products, and the terms change over time. We point you to the current offer on Microsoft's site and to your licensing partner. We do not quote license figures ourselves, so please check the latest terms there.

Can Business Central handle our project billing rules?

Standard projects support time and materials and fixed price billing, with work in progress recognition. Complex rules such as multi-tier rates or contract ceilings may need an add-on or a small extension. We test your hardest contract in a sandbox before you decide.

What happens to historical project data?

Open projects move with cost and billing to date, so reporting continues. Closed projects usually stay in an archived SL database or go to a reporting store. Bringing every old project transaction across is possible but seldom pays for itself. We help you pick the right scope.

We also use Dynamics GP in another entity. Can both move?

Yes. Each source has its own migration route. Both can land as companies in the same Business Central environment, sharing a chart design and dimensions. That is often the moment to set up intercompany postings and consolidation the right way, so group reporting works from day one.

Related reading for SL customers

Project accounting, ledger design and the wider cloud move each have their own page. Start with the comparison if you are still deciding whether to leave SL. Then read about the data steps. When you are ready to plan a Dynamics SL to Business Central migration, tell us about your projects and modules, and we will outline the work. For the product detail, see Business Central documentation on Microsoft Learn.