Microsoft Dynamics 365

Dynamics 365 Business Central Implementation

Business Central is Microsoft's cloud ERP for small and midsize companies. We set it up, move your data in from QuickBooks, Sage, NAV or GP, and write the AL extensions standard features don't cover.

Microsoft Dynamics 365
  1. 01New Business Central rollouts
  2. 02QuickBooks and Sage migration
  3. 03Dynamics GP migration
  4. 04NAV and on-premises upgrades
  5. 05AL extension development
  6. 06Integrations
  7. 07Reporting
Built withDynamics 365 Business CentralAL languageVisual Studio CodeAL-Go for GitHubBusiness Central admin center

At a glance

A Dynamics 365 Business Central implementation sets up Microsoft's cloud ERP for finance, sales, purchasing, inventory, warehousing and light manufacturing, and moves your data in from your old system. It fits growing companies from about 10 to a few hundred users. Tag4 Technology Solutions handles migrations from QuickBooks, Sage, NAV and GP, and writes AL extensions where standard features fall short.

Updated

Best for
Companies of about 10 to a few hundred users outgrowing their current system
Typical timeline
3 to 4 months for one company; 5 to 8 with manufacturing or several entities
Migrates from
QuickBooks, Sage, Dynamics NAV, Dynamics GP and on-premises Business Central
Customization
AL extensions built on events, so Microsoft's twice-yearly updates install cleanly
After go-live
Monthly support for questions, fixes, small enhancements and update testing
Offices
New York, Chicago, Dallas, Toronto, Sydney, Dubai

A Dynamics 365 Business Central implementation is usually triggered by growth. Your accountant is exporting QuickBooks into Excel to close the month. Inventory lives in a separate system that never quite matches the ledger. Or you're on Dynamics GP, and Microsoft has ended new GP sales and set a date for the end of support. Business Central handles finance, purchasing, sales, inventory, warehousing, light manufacturing, projects and service in one cloud system, and it fits companies from about 10 to a few hundred users.

The mistake we see most often is treating Business Central like a bigger QuickBooks. Teams skip the chart of accounts redesign, load every inactive customer, and set up posting groups by trial and error. Six months later nobody trusts the inventory valuation. We rebuild the chart of accounts and dimensions before any data moves, clean master data with you line by line, and test posting setups against real transactions from your last few months.

For NAV and GP customers, the other trap is dragging old customizations forward. Much of what was custom code in NAV is now standard in Business Central, and what isn't can usually be rebuilt as a small AL extension. We review each one and retire what you no longer need. GP and on-premises Business Central customers can use Microsoft's cloud migration tool for master data and history; QuickBooks and Sage data usually comes over through configuration packages and scripts.

A single-company rollout with standard finance and inventory typically goes live in 3 to 4 months. Add manufacturing, warehouse picking, several entities or complex integrations and 5 to 8 months is more realistic.

What we do

Dynamics 365 Business Central services

01

New Business Central rollouts

Setup of finance, sales, purchasing, inventory, warehouse and manufacturing modules, configured around how your team actually works.

02

QuickBooks and Sage migration

Chart of accounts redesign, customer and vendor cleanup, open AR and AP, opening balances and item data brought over in rehearsed loads.

03

Dynamics GP migration

A planned exit from GP using Microsoft's cloud migration tool plus custom handling for third-party modules and GP customizations.

04

NAV and on-premises upgrades

Upgrades from NAV 2009 through 2018 and older Business Central versions to the cloud, with C/AL code converted or replaced by AL extensions.

05

AL extension development

Per-tenant extensions built in Visual Studio Code with AL, source-controlled, tested with automated test codeunits and deployed through a pipeline.

06

Integrations

Shopify, Amazon, EDI, payroll, banking and shipping connections through Business Central APIs, AppSource apps or Azure Functions.

07

Reporting

Financial statements, Excel reports and Power BI dashboards built on Business Central data so managers stop asking accounting for exports.

How we work

What you can expect from us

AppSource before custom code

If a maintained AppSource app already solves your problem, we'll recommend it over building our own. You pay less and someone else keeps it current.

Two trial migrations

We run at least two full data loads before cutover and reconcile balances with your accountant each time, so go-live weekend has no surprises.

Sized for small teams

Your controller probably also runs payroll and HR. We keep workshops short, schedule testing around month-end and give you training videos you can reuse.

Upgrade-safe extensions

All custom logic lives in AL extensions using events, never modified base code, so the two major updates Microsoft ships each year install cleanly.

Tools and platforms

  • Dynamics 365 Business Central
  • AL language
  • Visual Studio Code
  • AL-Go for GitHub
  • Business Central admin center
  • Configuration packages
  • Cloud migration tool
  • Business Central APIs (OData / REST)
  • AppSource
  • Power BI
  • Power Automate
  • Azure Functions

Process

From first call to production

  1. Discovery

    A few working sessions to pin down goals, users, constraints and what "done" means. You get a written scope and estimate.

  2. Design

    Architecture, data model and clickable UI before heavy coding starts, so surprises show up early and cheaply.

  3. Build

    Two-week sprints with a demo at the end of each one. You see working software, not status reports.

  4. Launch

    Automated tests, staged rollout, monitoring and a rollback plan. Go-live should be boring.

  5. Support

    Bug fixes, updates and new features on a monthly plan, or a clean handover to your team.

FAQ

Dynamics 365 Business Central: common questions

How much does Business Central cost to implement?

Implementation cost depends on modules, data migration and integrations, and it is separate from Microsoft's monthly per-user license (Essentials or Premium, plus lower-cost Team Member seats). A focused finance and inventory rollout costs far less than one with manufacturing and several integrations. After a short discovery we give you a fixed-scope estimate by phase.

Is Business Central big enough for us, or do we need Finance and Operations?

Business Central covers most companies with up to a few hundred users, several legal entities and moderate manufacturing or warehousing needs. Finance and Operations is built for large, complex, often multinational operations and costs considerably more to license and implement. We'll tell you plainly if you've outgrown Business Central, but most midsize companies haven't.

What happens to Dynamics GP, and when should we move?

Microsoft stopped selling GP to new customers in 2025 and has announced end of support dates later this decade, after which security updates stop. You don't need to panic, but a move takes months and year-end tax updates are the first thing you'll miss. Planning the migration a year or more ahead gives you room to clean data and pick a quiet cutover date.

Can we bring our QuickBooks history into Business Central?

We usually migrate master data, open invoices and bills, and opening balances, plus monthly GL summaries for the prior year or two so comparisons work. Transaction-level history from QuickBooks rarely maps cleanly and is better kept in an archived company file. That keeps the new system clean and the migration affordable.

How long does a Business Central implementation take?

A straightforward single-company rollout takes 3 to 4 months. Projects with manufacturing, advanced warehousing, multiple entities or several integrations usually run 5 to 8 months.

Do you support Business Central after go-live?

Yes. We offer monthly support for user questions, fixes, small enhancements and testing extensions against each Microsoft update wave. Many clients also use it for new reports and the occasional process change as they grow.

Planning a dynamics 365 business central project?

Tell us what you are trying to build. An engineer reads every message and replies personally. No sales sequences, no pressure.