Moving from spreadsheets to one business system

Find the spreadsheet that is costing the most

Spreadsheets rarely fail because the formula is impossible. They fail because several people keep different copies, changes have no owner, and yesterday's sale must be typed again before today's report is useful. Start where that delay causes a missed sale, a wrong purchase, an unpaid balance or a late close.

Map the workflow from the first event to the management answer. For example: sale, payment, stock movement, customer balance, accounting entry and margin. Every handoff, duplicate entry and unexplained correction is part of the current cost.

Choose the smallest connected first release

Moving one isolated task can preserve the very retyping you are trying to remove. Pick two or three connected modules around the first pain. A retailer might begin with POS, stock and books. A growing service business might start with customers, billing and payments.

Write down what will not move in the first release. A clear boundary protects the launch from becoming an endless attempt to solve the whole company at once.

A good first release removes one complete chain of duplicate work from the business.

Clean decisions before you clean data

Data cleaning is faster after the business agrees what a product, customer, supplier, branch and account should mean. Decide the master naming rules, units, tax treatment, currencies, ownership and status values first. Then merge duplicates and archive records that no longer belong in daily work.

Keep a signed opening position for stock, customer balances, supplier balances, cash and bank. Those control totals are how you prove the new system started from the same financial truth as the old one.

Rehearse the busiest day, not the easiest demo

A rehearsal should use real volumes and awkward exceptions. Process the morning opening, a busy trading hour, a credit sale, a return, a stock receipt, an approval and the end-of-day close. If the business works through connectivity interruptions, test that too.

Compare the resulting sales, stock, cash, receivables and accounting totals with the control figures. Resolve the difference before launch. A discrepancy discovered in rehearsal costs minutes; the same discrepancy after a week of live trade costs days.

Train roles around decisions and exceptions

Cashiers, stock controllers, finance staff and managers do not need the same training. Each person should practise the work they own, the exceptions they can resolve and the escalation path for everything else. Give managers the reports and approval queues they must check from the first day.

Keep the old source read-only after cutover. Running two editable systems creates two versions of truth and guarantees a second reconciliation project.

Expand only after the first cycle closes cleanly

Set a short stabilisation period with a daily issue list, named owners and a decision on what blocks expansion. Once the first stock count, payroll cycle or month-end closes cleanly, add the next module or branch using the lessons already learned.

The supplier should leave you with a written scope, migrated totals, acceptance results, training record and support route. That evidence protects the investment long after the launch meeting.