Moving a company from spreadsheets to an ERP is mostly not a software task. The system can be ready in a day; the data, the habits and the cut-over date are what take planning. Consultants call this the cut-over: the moment the old way stops and the new system becomes the only record. Done well, it takes a few weeks of preparation and one quiet weekend. Done badly, the company runs both for months and trusts neither.
This article is the plan we recommend, in the order it should happen.
Step 1: Choose the cut-over date
Pick the first day of a month, ideally the first day of a quarter or of the year. Your opening balances are then the closing balances of the previous month, which your accountant already produces. Starting mid-month splits one month's accounting across two systems.
Decide also what you will not migrate. The standard answer: migrate master data and open balances, not history. Old invoices that are fully paid, closed orders and last year's stock movements stay in the spreadsheets as an archive. You need history only for analysis, and three months of live data in Voltrus will serve you better than three years of imported rows nobody trusts.
Step 2: Clean the data while it is still in Excel
Cleaning is ten times easier before import. Work through each list:
| List | Clean-up |
|---|---|
| Items | One row per real item. Unique SKU. Correct type (raw, finished or consumable). Base unit is the smallest unit you count. A realistic unit cost. Remove items not used in two years. |
| Customers | One row per legal entity. Consistent names. Payment terms written as days ("30" or "Net 30"). NPWP and tax status. |
| Suppliers | Same as customers, plus lead time in days, PKP status and bank details. |
| Stock | A physical count close to the cut-over date, by item and warehouse. |
| Receivables and payables | A list of every unpaid customer invoice and supplier bill, with number, date, due date and amount, agreed with your accountant. |
Read Master data and transactions before you start: most of its rules are clean-up rules.
Step 3: Set up the company
Before importing anything, set the things everything else depends on:
- Settings → General: company name, address and the timezone (it decides which calendar day a posting falls on).
- Settings → Tax: your NPWP, NITKU and the PPN rate.
- Settings → Inventory & trading: the costing method (moving average, FIFO or standard; see Inventory valuation), credit control and the bill price check. Choose the costing method now: switching later with stock on hand needs a revaluation.
- Settings → Ledger: review the GL accounts and map them to your existing chart if you have one. Voltrus creates its default accounts automatically on first posting; you can rename them or add your own.
- Warehouses and bins, if you use more than the default
MAINwarehouse. - Users & tokens: create the people and give each a role (Admin, Ops or Viewer). Make at least one person Admin first.
- Approval limits: in Settings → Inventory & trading → Approvals and limits, set the amounts above which a purchase order, a supplier bill or a payment needs an admin.
Step 4: Import master data
Onboarding imports from CSV or an Excel file (the first sheet is used). Download the template for each kind, fill it, and upload.
| Kind | Columns |
|---|---|
| Items | sku, name, type, uom, unit_cost, reorder_point |
| Suppliers | name, terms, lead_time_days |
| Customers | name, terms |
| Opening stock | item_sku, qty, reason |
| Open customer invoices | number, customer, issue_date, due_date, currency, fx_rate, amount_open |
| Open supplier bills | number, supplier, issue_date, due_date, currency, fx_rate, amount_open |
Comma and semicolon delimiters both work, so files saved from Indonesian-locale Excel import as they are. Each row is processed on its own: bad rows are listed with the reason, good rows import anyway. Rows whose key already exists (the same SKU, supplier or customer name, or invoice number) are skipped, so you can fix the errors and run the same file again safely.
The importer covers the essential columns. Fill the rest (tax IDs, credit limits, price lists, planning parameters, unit conversions) in the record screens afterwards, or by an agent working through the governed flow. If you come from Epicor, Onboarding can also import items, suppliers, customers and on-hand stock directly; run its report first to preview, then apply.
Step 5: Load opening balances
This is the step that makes the books continuous. On the cut-over date you need, in Voltrus, the same balance sheet your old books show.
- Opening stock. Import the count with reason
receipt. Stock is valued at each item's unit cost, so check the costs first. - Open receivables and payables. Each unpaid customer invoice and supplier bill must exist as its own record, with number, date, due date and amount, so that later payments can be applied to it one by one; a single "AR balance" figure cannot be collected. Import them in Onboarding as Open customer invoices and Open supplier bills.
amount_openis what is still owed, PPN included, in the invoice's currency (fx_rateis required for foreign currencies). They arrive already issued and without a journal, because their revenue, cost and PPN already sit in your old books. Payments later settle them like any other invoice. Open invoices are also left out of the Coretax export, since their fakturs were made in the old system. - The opening balance journal. Settings → Ledger → Opening balance builds one journal on your cut-over date from records that have not posted a journal yet: open invoices and bills, imported stock, and a few others (goods received not invoiced, work in progress, customer advances). You add manual lines for what Voltrus cannot know: bank and cash balances, fixed assets and accumulated depreciation, loans, paid-in capital, and any tax still owed to the tax office. Whatever does not balance goes to Opening balance equity (3-9000).
Opening balance journal, 1 April
Dr Bank BCA 250,000,000
Dr Accounts receivable 180,000,000 (from open invoices)
Dr Inventory 420,000,000 (from opening stock)
Dr Fixed assets 900,000,000
Cr Accumulated depreciation 300,000,000
Cr Accounts payable 140,000,000 (from open bills)
Cr Bank loan 400,000,000
Cr Opening balance equity 910,000,000
Step 6: Train, then run in parallel briefly
Train each team on its own documents, using real examples from your business, in a test session before go-live. People learn the PO screen by entering last week's POs, not by watching a demo.
Then run a short parallel period: one or two weeks where the team works in Voltrus and someone also keeps the old spreadsheet, to compare. Agree the end date in advance. Any difference you find is either a data problem to fix or a habit problem to coach.
Step 7: Switch off the spreadsheets
On the agreed date, the old files become read-only archives. Move them to a folder named "archive", remove edit rights, and tell everyone. From now on, a number that is not in Voltrus does not exist.
Then close the first month properly using The month-end close checklist. The first close always finds a few problems; that is its purpose.
A realistic timeline
| Week | Work |
|---|---|
| −6 | Choose cut-over date, name owners per area |
| −5 to −3 | Clean master data in Excel; company settings in Voltrus |
| −3 | Import master data; fix errors; complete details |
| −2 | Training on real examples |
| −1 | Physical stock count; list open AR and AP |
| 0 | Import stock and open invoices and bills, post opening balance; go live |
| +1 to +2 | Parallel check, then archive the spreadsheets |
| +4 | First month-end close in Voltrus |
Checklist
- Cut-over date fixed on the first day of a month.
- Master data cleaned, coded and owned before import.
- Costing method and tax settings chosen before any stock is loaded.
- At least one Admin user and the approval limits set.
- Every open invoice and bill imported individually before the opening balance; opening balance journal posted and reconciled.
- Parallel run with a fixed end date, then spreadsheets archived read-only.