The short answer
Do not start by importing every spreadsheet into a database. Start by defining which record is authoritative, what each field means, how updates are approved and how staff will work after the change. Migration succeeds when the new workflow is clearer than the old files.
Step 1: Catalogue the spreadsheets and what each one controls
List the workbook owner, last update, purpose and downstream users for each file. A booking register, occupancy sheet and finance reconciliation workbook may reference the same identifier but disagree about what it means. Record those differences rather than hiding them during consolidation.
Step 2: Choose the authoritative record for each kind of information
Decide which source controls customer details, room status, job hours or invoice data. A new application may become the home for operational status while an accounting package remains the source of truth for financial transactions. One system does not have to contain every function; it needs explicit boundaries and reliable handovers.
Step 3: Clean and validate data before importing it
- Standardise dates, reference numbers and status values
- Identify duplicates and records missing a unique identifier
- Document formulas that calculate business-critical figures
- Separate historical records from those actively used
- Decide how to resolve conflicting values and who approves corrections
Step 4: Design the actual workflow
For every record, document who creates it, who may edit or approve it, what the valid status changes are and what report depends on it. A form is not automatically a workflow. A workflow must explain what happens when a required field is missing, a booking is cancelled or an approval is rejected.
Step 5: Run a limited pilot alongside the old process
| Pilot check | What to verify |
|---|---|
| Record completeness | Every required field and linked attachment is present |
| Permissions | Staff see and edit only the information relevant to their role |
| Reconciliation | Totals and statuses can be explained against the original records |
| Exceptions | Cancelled, duplicate and corrected entries follow the agreed path |
| Reporting | Managers can reproduce the decisions they previously made from worksheets |
Step 6: Agree a cutover and a rollback plan
Set a final migration window, record owners, validation sign-off and a way to recover if important information does not reconcile. Retain original records for the period required by your organisation and applicable obligations. Where tax records are involved, consult the ATO guidance rather than assuming a successful import removes the need to retain source documents.
Frequently asked questions
Can we import our old Excel files directly?
Sometimes, but duplicate records, free-text statuses and formulas often need mapping and validation before import.
What happens to the old spreadsheets?
Keep them available under an agreed records and rollback plan. The retention period depends on the information and relevant requirements.
Further reading and sources
These external sources provide general Australian guidance, not project pricing or specific BPA Solutions customer outcomes.
Want to discuss the workflow behind the question?
Share the process you are trying to improve, the tools you use today and the decisions that need to happen. We can discuss a practical starting point without assuming you need a complete replacement.
Get my free automation assessment