D365ConsultantDivision of Sataware
Talk to an expert
D365ConsultantDivision of Sataware
Sage 100 migration

Sage 100 to Business Central migration, module by module.

A Sage 100 to Business Central migration is rarely just an accounting move. Sage 100 systems, still called MAS 90 or MAS 200 by long-time users, tend to be built from many modules plus third-party enhancements and user-defined fields added over the years. The plan has to account for every one of them.

Visual Integrator
Sage 100's own import and export tool
Item tracking
lot and serial numbers in Business Central
Premium
Business Central licence needed for production orders
Team leaning over a laptop in a meeting room

Inventory the enhancements before anything else

Sage 100 has a large ecosystem of third-party enhancements, and many systems run several. Some add fields, some change how sales orders or purchasing behave, and some are whole modules for EDI, freight or shop floor tracking. They are also the part of a Sage 100 system least likely to be documented.

Before mapping data, we list every enhancement, every Custom Office user-defined field and every custom report. For each one the question is the same: does standard Business Central already do this, is there an AppSource app that does, or does it need an AL extension? Some enhancements exist to fill gaps that Business Central covers as standard, such as multiple ship-to addresses, analysis by dimension or approval workflows.

That answer shapes the effort more than data volume does, which is why it comes first.

Sage 100 modules and their destinations

General Ledger

Account segments become a main G/L account plus dimensions. Sage 100 budgets can be loaded as G/L budgets by account and dimension.

Accounts Receivable

Customers, including those grouped under AR divisions, become customers. The division is kept as a dimension or a posting group, so division-level aging still works.

Accounts Payable

Vendors, terms and 1099 settings move across. Business Central handles US 1099 reporting as standard, so vendor 1099 codes are mapped rather than rebuilt.

Sales Order and Purchase Order

Open orders are recreated as documents. Back-ordered quantities become the outstanding quantity on the Business Central order line.

Inventory Management

Items, warehouses and quantities map to items, locations and item journal entries. Lot and serial numbers become item tracking.

Bill of Materials and Work Order

Bills become production BOMs or assembly BOMs, depending on how you build. Open work orders become released production orders.

Valuation methods compared

Sage 100 method
Business Central method
Notes
Standard
Standard
Standard costs loaded on the item card, with variances posted from then on
Average
Average
Average cost period chosen in inventory setup
FIFO
FIFO
Opening cost layers loaded as separate journal lines
LIFO
LIFO
Same approach as FIFO, one line per layer
Serial
Specific
Each serial number carries its own cost
Lot
No direct match
Choose FIFO or Average and keep lot tracking for traceability

Getting data out: Visual Integrator, ODBC and SQL

  1. 1

    Visual Integrator jobs

    Sage 100's Visual Integrator exports module tables to delimited files. Export jobs are saved and rerun on cutover day, so the rehearsal and the final extract use identical definitions.

  2. 2

    ODBC for Standard and Advanced

    Sage 100 Standard and Advanced keep data in Sage's own file format, readable through the ODBC driver Sage supplies. We use it for record counts and reconciliation queries.

  3. 3

    SQL Server for Premium

    Sage 100 Premium runs on Microsoft SQL Server, so extraction and checks are written as SQL queries against a copy of the database.

  4. 4

    Rehearse, then cut over

    A full rehearsal loads everything into a Business Central sandbox and reconciles it. Cutover repeats the same jobs against the final data, with the same checks.

Open work and in-flight documents at cutover

Distribution and manufacturing companies rarely have a quiet day. On any cutover date there will be orders picked but not invoiced, goods received but not billed, and work orders half complete. Each needs a written rule.

Picked orders are invoiced in Sage 100 before cutover wherever possible. Goods received but not yet invoiced are carried as an accrual in the opening balances, with the matching purchase lines recreated so the vendor invoice can be entered in Business Central when it arrives. Partly complete work orders are either finished in Sage 100 or brought over with the components already issued valued as work in progress.

Agreeing these rules with the warehouse and the controller before cutover day is what keeps shipping on schedule the morning after.

Hand sketching on a sheet of paper at a desk
Hand sketching on a sheet of paper at a desk

Sage 100 migration questions

We have a lot of customizations. Is Business Central realistic?

Usually, but only once the list of customizations is sorted. Often some turn out to cover things Business Central does as standard, and some are no longer used at all. What remains is rebuilt as AL extensions, which stay intact through Microsoft's updates. The customization list is the first document we ask to see.

Can we keep our AR divisions?

Yes, in effect. Business Central has no division prefix on the customer number, but a dimension or a customer posting group per division gives the same aging and reporting split. If divisions post to different receivables accounts, posting groups are the natural fit; if they only matter for reporting, a dimension is lighter.

Do we need Business Central Premium?

Only if you run Sage 100 Work Order today or plan to use production orders and capacity planning. Assembly BOMs, which cover kitting and simple builds, are available in Essentials. We look at how your work orders are actually used before recommending a licence.

How is Sage 100 history handled?

Detailed history stays in Sage 100, which can be kept on one machine for lookups. Business Central receives open documents, balances and, if you want trend reports, monthly net change by account and dimension for prior years. Sales history by customer and item can also be loaded into Power BI if your sales team relies on it.

What does the scoping call cover?

Your modules, enhancements, user-defined fields, integrations and entities, plus the reports your management team reads every month. From that we write a scope for you to approve. We do not quote figures before that written scope exists.

Talk to us about your project.

Tell us what you run today and what has to change. A senior consultant replies with a written next step.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.