Cabinet Making Software Migration: Keep Live Jobs and Records Intact
Plan your cabinet making software migration: preserve job history, reconcile stock and balances, and test live workflows before your workshop changes systems.

The short answer
A migration is ready when the next job can move forward correctly and an old job can still be explained. Agree what transfers, what is archived and what must be rebuilt, with an owner for each record group. Take a readable export before anything changes, rehearse a handful of real jobs, reconcile them record by record, and only then set a changeover time and close the old system.
Monday's kitchen is still due for assembly. Its approved drawing is in the old job system, the remaining hinges are on a partly received purchase order, and the deposit is already recorded in your accounts. A new login does not prove that any of those details have arrived correctly.
A cabinet making software migration needs a clear handover for the work your business is already doing. This guide shows how to define the transfer, test representative jobs, reconcile the results and keep older records readable before you stop relying on the previous system. It applies whether you are leaving a legacy job system or a set of spreadsheets.
Why check this now
Software access can end on a date you did not choose. Providers retire older products, end support for them and set a final date for read-only access to the old copy. If your current system has an end date, get it in writing, along with what you can still export before then.
The same applies to any system: the day old access ends is a poor day to discover what the export left out.
The steps below are suggested operating practice, not an industry standard, and not legal, tax or accounting advice. No reliable Australian figure exists for how long a migration takes or what it costs, so this guide gives checks you can inspect instead of a timeline.
1. Decide what moves, what stays and who owns it
Start with a short scope meeting: the owner, the office lead, the production lead and the bookkeeper. Answer two questions first. Which systems are changing (job management, accounting, design software, or several at once)? And which record currently controls each business decision?
If you are still deciding whether to replace spreadsheets at all, first compare cabinet software with spreadsheets. This guide assumes the decision is made.
Name the authoritative source for contacts, approved quotes, drawings, job status, stock, purchase orders and issued invoices. Keep customer-approved documents separate from editable estimates. Then put every record group into one of four classes:
- Transfer for active use in the new system.
- Retain in a searchable archive.
- Rebuild and test in the new system.
- Review separately before disposal.
"Archive" needs a named location, a person responsible and a way to retrieve a record. Do not quietly leave out closed jobs that still have an open defect, a credit or an unpaid balance.
A scope worksheet
| Record group | Owner | Acceptance evidence |
|---|---|---|
| Live jobs | Production lead | Every original job ID has a checked destination and current stage |
| Invoices and payments | Bookkeeper | Existing document identities and balances remain correct |
| Drawings and approvals | Drafting lead | The correct approved revision opens from the mapped job |
| Templates and automation | Office lead | Rebuilt outputs and triggers pass a test |
Configuration is its own scope
Settings often do not travel with data. Document templates, custom reports, automated triggers and forms commonly have to be set up again, sometimes even when you move between two products from the same provider. Assume nothing about a move between providers. Ask your new provider for its supported formats and its exclusions in writing, and put each excluded item on the rebuild list with an owner.
Deliverable: a signed scope sheet with a named owner for every record group.
2. Capture a readable baseline before changing anything
Two questions decide whether your baseline is good enough. Can the business recover the source records? And can someone read the export without the old subscription?
Ask the current provider for:
- Structured exports (spreadsheet or CSV) of each record group.
- Readable documents such as quotes, invoices and purchase orders as PDFs.
- Attachments, drawings and photos as actual files.
- Approval evidence: who accepted what, and when.
- Historical identifiers such as job, quote, order and invoice numbers.
- Field definitions, so a column heading can be understood in three years' time.
Keep the originals untouched and clean a copy. Record the export time, the timezone, any filters applied and the periods included.
Check for links that will die
Open the export on a computer that is not signed in to the old system. An export that lists a drawing as a web link back to the old system is not an archive of that drawing. When access ends, the link ends with it. The file itself needs to be in your storage.
Then run one retrieval test: find a completed job in the proposed archive and open its accepted quote, its drawing and its invoice.
If you are moving from spreadsheets
Spreadsheets have their own traps:
- Several versions of the truth. Agree which file, and which tab, is the master before copying anything.
- Hidden rows and filters. A filtered sheet can export only what is visible. Clear filters and unhide rows first.
- Formulas. A CSV keeps the result, not the formula. Record the pricing rules that live inside cells before they are flattened.
- Codes that change on opening. Spreadsheet programs can drop leading zeros and turn some codes into dates. Format code columns as text and spot-check them after export.
- Meaning held in colour. A red cell that means "on hold" will not import. Turn colours and cell comments into real columns.
How long records need to stay readable
Cancelling software is not a retention plan. The Australian Government's record keeping guidance says most business records must be kept for 5 years, from when you got the record or completed the transaction, whichever is later, and that company records and some employee records need 7 years. It also says digital records must be stored so they cannot be changed or damaged, on a device you can access, have backed up and control. The ATO's small business course gives the same core rules: keep your records, do not change them, keep most for 5 years, show them to the ATO if asked, and keep them in English.
The Fair Work Ombudsman says employers must keep time and wages records for 7 years, and that they must be legible, in English and readily accessible to a Fair Work Inspector.
These are existing obligations, not new migration rules, and periods differ by record type. Ask your accountant to confirm what applies to your business. Five years is not a universal deletion date.
Keep employee records restricted. A job-system migration is no reason to copy payroll or identity documents into a folder the whole workshop can open. For the provider side of this, see how to check a provider's access and export arrangements.
Deliverable: an export manifest listing each file, the period it covers, the result of its opening test, where it is stored and who is responsible. Get the old provider's final access date in writing.
3. Map meanings and relationships before importing
Importing rows does not prove that relationships survived. A job is useful because it points to a client, a site, an approved drawing, its materials and its invoices. Before any import, write down what each field means and what it connects to.
Does "complete" mean manufactured, installed or financially closed? Is the hardware quantity in pieces, pairs or packs?
Build a mapping table with the source value, the destination value, the conversion rule and the person who approved it. Cover:
- Original and destination job IDs.
- Client, site and supplier relationships.
- Material codes, finish and thickness.
- Quantity and measurement units (millimetres or inches, hours or minutes, pieces or pairs).
- Dates, status meanings and tax basis (GST inclusive or exclusive).
- Approved drawing revisions, and the jobs they apply to.
Keep a supplier's product code separate from a free-text description.
Stock is three numbers, not one
Separate physical stock, reservations and incoming orders. For purchase orders, keep ordered, received, cancelled and remaining quantities distinct. A partly received order imported as fully outstanding can trigger a second order. Imported as fully received, it hides a shortage.
An illustrative check:
| Hinges | Quantity |
|---|---|
| Physically held | 40 |
| Reserved for jobs | 30 |
| Still on order | 20 |
| Unreserved today | 10 |
The 20 on order are not available today. Confirm how the new system shows each of the three figures. If reservations are new to your workshop, the same thinking applies to how you allocate sheet materials to the right job.
CAD/CAM is a separate engineering scope
Treat cabinet libraries, machine settings, tooling data and NC programs as their own agreed scope with their own tests. A job-record import does not validate machining output. Nothing reaches a machine from a migrated library until someone competent has checked it on that machine.
Deliverable: approved mappings and an exception list. No silent guesses for missing units or unclear statuses.
4. Rehearse real jobs and reconcile the result
A rehearsal answers two questions. Can staff perform the next real action on each job? Do identities, quantities and balances agree with the source?
Use a test environment or a controlled dataset approved by the provider. Isolate anything that reaches the outside world: test emails, purchasing, writes to the accounting system and machine output.
Choose representative cases:
- An accepted job awaiting production.
- A partly received materials order.
- A revised drawing with a part-paid invoice.
- A completed job with an open service issue.
Trace each one from its original ID to its new record, its attachments, its remaining tasks and its financial references.
Compare records, not only totals
Matching totals can hide errors that cancel out. Twelve jobs exported and twelve imported could still contain one duplicate and one omission. Match on the original job ID, one by one.
A reconciliation example
This example is hypothetical. All amounts use the same GST basis.
| Item | Checked source value |
|---|---|
| Accepted contract | $33,000 |
| Invoices already issued | $11,000 |
| Payments applied | $4,400 |
| Outstanding invoiced amount | $6,600 |
| Contract value not yet invoiced | $22,000 |
The outstanding $6,600 is the $11,000 invoiced less the $4,400 paid. Keep the $22,000 of unbilled contract value separate from existing receivables. A common failure is importing the whole contract as one unpaid invoice, which overstates what the customer owes today.
Preserve existing invoice numbers, and do not let the new system send historical invoices to your accounting ledger a second time. Your bookkeeper confirms the accounting treatment. The example shows a reconciliation check, not a tax treatment.
Log every discrepancy
For each difference, record the source record, the expected result, the actual result, an owner and the retest outcome. Have the estimator, the production lead and the bookkeeper each sign off the checks that concern their work.
Deliverable: completed trial-job checks and reconciled control totals.
5. Set a controlled changeover and a recovery decision
Agree a precise local date and time for the switch, who is available for support, and the last permitted entry in each system. From that moment, one system owns new operational entries.
Anything that happened after the baseline export (a receipt, a payment, a drawing change) goes on a changeover log so it transfers once. Not zero times, and not twice.
Choose a quiet moment
Avoid the middle of a pay run, the end of a BAS period, and the week of a large installation. The weeks around a Christmas shutdown can look ideal because production is quiet. Check first that your provider's support team and your bookkeeper are working those days.
Keep any parallel run short
Running both systems side by side feels safe, but it means double entry, and every double entry is a chance for the two to disagree. If you run in parallel, set an end date and state which system is authoritative for each record type during the overlap.
Proceed only when
- Live jobs and their immediate next actions are checked.
- Critical quantities, references and balances have no unexplained differences.
- Drawings and essential documents open for the people who need them.
- Ownership of each integration is agreed.
- Staff can perform their first tasks.
- Archive retrieval and the recovery arrangement are verified.
What blocks the switch
Minor issues can travel with you if each has an owner, a workaround and a due date. Three things should hold the changeover: missing approvals, unexplained differences in critical balances, and any untested risk of posting the same transaction twice to accounting or to a supplier.
Agree the recovery path first
Agree with both providers what going back would involve. Reverting is not simply changing a login. Every transaction created after the switch has to be accounted for in the old system. Do not assume an unsupported legacy system can safely return to production use.
Deliverable: a proceed or hold decision approved by the owner, and a dated changeover transaction log.
6. Verify the first working cycle and close old access deliberately
Assign one contact for early problems and review open issues daily while the changeover settles. Check the first real instance of each core transaction:
- The first purchase order.
- The first goods receipt.
- The first labour entry.
- The first invoice.
Did each behave as it did in the rehearsal? After any fix, reconcile the affected records again.
Prove an old job can still be explained
Pick a historical job and retrieve its accepted scope, its drawing, its invoice and its payment evidence from the retained archive. Confirm that the retrieval does not depend on an account that is about to expire. Keep an index showing where historical information lives and who can retrieve it.
Retire the old system last
Close old accounts and disconnect old integrations only after the agreed checks and the retention arrangements are complete. A forgotten integration can keep writing to your accounts after everyone has stopped looking at it.
What to measure
Track five counts through the first cycle:
- Unmatched active jobs.
- Unexplained balance differences.
- Inaccessible attachments.
- Duplicate external postings.
- Unresolved critical issues.
Each should reach zero and stay there. These are operating checks for your own business, not industry benchmarks.
Deliverable: a signed first-cycle review and one successful historical-record retrieval.
Start with one live job and one completed job
Before you plan the whole transfer, pick two jobs.
- One live job. Prove it can move forward in the new system with the right scope, parts and balances.
- One completed job. Prove its history stays readable without the old login.
Whatever those two jobs expose becomes your checklist. Then run the same checks across the full transfer before you end access to the old system.
Frequently asked questions
What should be migrated when changing cabinet making software?
Sort every record group into four classes: transfer for active use, retain in a searchable archive, rebuild and test in the new system, or review separately before disposal. Live jobs, open purchase orders, current stock and unpaid invoices usually need to transfer or be linked. Templates, reports and automations often have to be rebuilt. Closed jobs can sit in an archive, but keep any with an open defect, credit or unpaid balance in scope.
How long do I need to keep records from the old system?
Australian Government guidance says most business records must be kept for 5 years, with company records and some employee records needing 7 years. The Fair Work Ombudsman says time and wages records must be kept for 7 years, legible, in English and readily accessible. Periods differ by record type, so confirm yours with your accountant. Make sure the archive can be opened without the old subscription.
Should we run the old and new systems in parallel?
Only for a short, fixed period. Parallel running means double entry, and each double entry is a chance for the two systems to disagree. If you do it, set an end date and state which system is authoritative for each record type during the overlap. A rehearsal on real jobs before the switch usually finds more problems than a long parallel run after it.
Does a job-record migration cover CAD/CAM libraries and machine programs?
No. Treat cabinet libraries, machine settings, tooling data and NC programs as a separate engineering scope with their own tests. Importing job records does not validate machining output. Nothing should reach a machine from a migrated library until a competent person has checked it on that machine.
How can CabiPro help with a software changeover?
CabiPro can import clients, contacts and suppliers from an Excel or CSV file, and it checks every row before anything is added. Projects, production stages, dates, assigned teams and job notes then hold the live work in one place. Live jobs, quotes, drawings, purchase orders and invoices are not imported automatically from another system, so agree in a demo what transfers, what needs rebuilding and how you will verify it.
Sources and further reading
- Australian Government: Record keeping - general 5 year period, 7 years for company and some employee records, and storage rules for digital records. No update date shown.
- ATO: Record keeping fast facts - the five core record keeping rules for small business.
- Fair Work Ombudsman: Record-keeping - time and wages records kept for 7 years, legible, in English and readily accessible to a Fair Work Inspector.
Sources checked on 13 November 2026. The workshop, jobs, quantities and dollar figures are hypothetical. This article is general information, not legal, tax or accounting advice.
More from the shop floor
Test your changeover on one real job.
Bring a representative live job and your migration checklist to a CabiPro demo. See how its stages, dates, team assignments and notes would be managed, then agree what can be transferred, what needs rebuilding and how you will verify the result before setting a changeover date.