When should a South African business move from Sage or Pastel to Business Central?

Sage and Pastel can be perfectly sensible choices for a growing business. Moving to an ERP system is not automatically progress: a migration is disruptive if the new system does not solve a real operational problem.

The question is not whether your accounting package is old. It is whether your staff can still manage purchasing, stock, sales, finance and reporting without maintaining several versions of the truth.

Five signs it is time to investigate ERP

1. Inventory is reconciled in spreadsheets. Stock quantities and stock values come from different places, and people spend time explaining the differences.
2. Order processing crosses too many systems. A sale is captured in one place, picked in another and invoiced elsewhere.
3. Month-end depends on a few key people. Manual reconciliations are difficult to repeat and hard to audit.
4. Management reporting arrives too late. A weekly performance report takes days to assemble, so decisions are made with older information.
5. Workarounds are becoming permanent. Each new customer, site or product range introduces another manual file or custom step.

One of these is not proof that you need Business Central. Together, they are a reason to map your processes and calculate the cost of the current arrangement.

What Business Central can connect

Microsoft Dynamics 365 Business Central combines areas such as financial management, sales, purchasing, inventory and other operations in one ERP platform. It can connect to other services through published APIs and be extended where standard functionality does not match a business requirement.

That does not mean every business needs every module or should customise everything. Good implementations use standard features where they fit and add only the changes that have a clear benefit.

What an implementation really involves

1. Discover the current process

Walk through a real order from quotation to payment and a real purchase from requisition to supplier settlement. Identify approvals, exceptions, reports and hand-offs that staff rely on.

2. Agree what moves

Create an inventory of customer, supplier and item master data, open documents, balances and historical transactions. Decide which history belongs in the new system and which can remain in a secure archive.

3. Clean and test the data

Remove duplicate records, agree on codes and validate opening balances. Do a trial migration early enough to find issues while they are still inexpensive to fix.

4. Test complete business scenarios

Test everyday work and unusual situations: returns, partial deliveries, credits, stock adjustments and month-end. Have actual end users sign off, not just the project team.

5. Prepare the cutover

Assign an owner to each step. Decide when capture stops in the old system, how opening positions are checked and who is available to help on the first working day.

Microsoft documents company configuration packages and data migration options. The correct migration method depends on the source system and the data being moved.

Ask these questions before requesting a quote

• Which workflows are included and which are excluded?
• How will historical data, opening balances and VAT-related reporting be reconciled?
• What integrations and extensions are required?
• Who owns master-data cleansing?
• What is the test, training and support plan?
• Which licence, implementation and ongoing support costs are separate?

A price without agreed scope is only a guess.

A sensible first step

Before selecting a product, write down the three processes causing the most wasted effort. Map how data moves today and what a successful improvement would look like.

If that exercise points towards ERP, use our contact form to discuss a practical assessment of your requirements.