The Suniworks journal
When should you replace Excel with a business application?
Repeated corrections, competing copies and manual transfers can turn a useful spreadsheet into an operational concern. Assess the process behind the workbook, compare suitable alternatives and prepare a migration you can check before committing to it.
Updated on .

Consider replacing Excel with a business application when keeping records reliable requires repeated reconciliation, manual corrections or the knowledge of a particular colleague. Base the decision on the consequences for your operations and the rules you need to enforce, rather than the size or apparent complexity of the workbook.
For an SME owner or operations manager in French-speaking Switzerland, the useful starting point is a specific task: processing orders, scheduling work or preparing information for accounts. Establish what needs to change before deciding whether to improve the spreadsheet, choose existing software or commission an application.
The decision at a glance
- Keep Excel where a well-understood calculation or analysis meets the need.
- Investigate alternatives when maintaining dependable operational records requires recurring workarounds.
- Compare solutions using the same business case, including exceptions, data preparation and ongoing responsibilities.
Identify the job that has outgrown the workbook
Describe the operational problem before choosing its replacement. A confusing report, an unclear approval and repeated copying into accounting software are different problems. Treating them as a general complaint about Excel makes it harder to judge whether a proposed solution addresses the cause.
Microsoft documents Excel co-authoring, including requirements relating to software versions and workbook storage. Check your actual configuration before treating competing copies as an inherent limitation of spreadsheets. The linked guidance is in French.
Separate analysis from operational decisions
A workbook used to explore possible prices has a different role from one used to authorise production. In the latter case, ask who approves the work, what may change afterwards and how that decision is recorded. Describe the operational exposure before selecting a replacement.
Consider a hypothetical joinery business. Comparing material options in a spreadsheet may meet the workshop’s needs. If the same file also determines which orders can enter production, assess that approval process separately. The requirement to investigate is an identifiable authorisation, rather than a more attractive version of the worksheet.
Resolve disagreements about the process first
Ask the team when an approved order may change and who can accept an exception. If their answers differ, agree the rule before requesting an automatic check. Software cannot settle a business decision that has not been made.
Write down the agreed rule in everyday language. Include the person responsible for deciding an exception. That description remains useful whether you retain Excel or move elsewhere, and gives a prospective supplier something more precise than a collection of tabs to reproduce.
Gather evidence from everyday work
Record each incident, its consequence, its observed frequency and how it was detected. Competing copies, repeated entry and dependence on one colleague are prompts for investigation, rather than an automatic reason to migrate.
Find where people establish the current position
When copies circulate, ask how staff determine which record is authoritative. Do they reconcile messages, ask a colleague or compare files before acting? Note whether an order or invoice has already been processed by the time the discrepancy is resolved.
Avoid concluding that Excel has no collaboration facilities: Microsoft explicitly includes collaboration in its help resources. Investigate the arrangement your team actually uses. A documented collaboration feature and a working practice based on independent attachments are different things.
Follow information between tools
Trace a customer detail or order change from its first entry to its final use. Record every manual transfer and every place that needs updating after a correction. Connecting the existing tools may resolve the issue without replacing the workbook.
For each proposed connection, specify what information moves, its direction and the event that triggers it. Ask the supplier to demonstrate that exchange. An application proposal that leaves the existing transfers unexplained has not yet addressed the full task you are trying to improve.
Make essential knowledge transferable
Ask the workbook’s main user to explain important calculations and manual adjustments. Document the business rules, then ask the process owner which ones remain valid.
Distinguish a current pricing rule from an abandoned practice or temporary workaround. Do not require the replacement to preserve every behaviour simply because it exists in the spreadsheet. Have the process owner confirm what the application should do, including where it should deliberately differ.
Compare alternatives on the same working example
Assess four options using the same working case and its exceptions: improving the workbook, choosing an existing product, configuring a no-code platform or commissioning an application. Include both initial expenditure and continuing operation.
The comparison below sets out questions to investigate. It does not rank individual products or assume that every application includes the same capabilities.
| Option | When to investigate it | What to establish |
|---|---|---|
| Improve the workbook | The task is contained and the main difficulties concern structure or consistent entry. | Would clearer records and explicit entry rules resolve the observed problems? |
| Choose existing software | Your process can follow an established way of working. | Which changes would your team need to accept? |
| Configure a no-code platform | The task fits the platform’s forms and available rules. | Are its constraints, subscriptions and data arrangements acceptable? |
| Commission a bespoke application | Company-specific rules, different responsibilities or software connections need to be implemented. | Does the defined scope justify development and ongoing maintenance? |
Test exceptions, permissions and history
A business application is software organised around a task, such as processing orders or coordinating interventions. Specify the input checks, permissions and change records you require. A different interface does not guarantee these capabilities.
Ask what happens when required information is missing or someone tries to amend an approved record. In a hypothetical retail business, demonstrate cancellation after order preparation. Check who may perform it, what happens to related information and how another employee can understand the resulting record.
Name the person who will approve business rules and agree acceptance tests before development. Suniworks describes staged reviews in its development method. Specify who will correct defects and support the application afterwards.
Allow a reasoned decision to wait
Retaining Excel can be a deliberate choice while an activity is new or working practices remain unsettled. Document the file and agree responsibilities, then record a concrete trigger for reviewing the decision.
Record what would trigger another review: a specific incident, a new approval requirement or a necessary connection to another tool. This gives the team a practical reason to reopen the decision, rather than returning to it whenever the workbook feels cumbersome.
Build a cost comparison from observations
Compare observed work in the current arrangement with priced proposals for the alternatives. Include preparation, licences, configuration or development, hosting and maintenance. Check what is already included in each offer to prevent double counting.
For the current process, record time spent consolidating files, correcting entries and transferring information. Separate documented correction costs from hypothetical losses. A known invoice correction can enter the assessment; an assumed missed sale should not become a promised saving.
For each proposed solution, request separate provision for preparation, data transfer, configuration or development, subscriptions and maintenance. Include the availability required from your own staff to explain rules, check results and help colleagues adopt the new process. Compare the alternatives over the same period, chosen for your decision.
Ask where data will be held, who can access it and how it can be recovered. Record the answers for the proposed application and agree the export and handover arrangements before committing.
Design a migration that can be checked
Choose a bounded process whose results the team can verify. Prepare the data, test representative cases and extend use only after the process owner accepts the results.
Define acceptance before discussing screens
Describe the required outcome of an operation: an order has a responsible person, its approval can be identified and subsequent changes follow an agreed rule. Include authorised exceptions. Use those statements to assess the proposal and later determine whether the delivered behaviour is acceptable.
Involve daily users in defining acceptance. Ask what they need to finish each task and which workarounds they rely on. Have the process owner confirm the expected results.
Prepare records and expected results
Check duplicates, inconsistent values and date formats before importing records. Decide which history must remain accessible and which records are required for continuing operations.
Prepare comparison cases covering routine work, an exception and an incomplete record. Have the process owner approve the expected outcome for each. When the application and workbook disagree, explain the difference before accepting it: either the new behaviour needs correction or an older rule needs reconsideration.
Decide when the old workbook stops changing
Specify where staff enter new transactions during comparison, who investigates differences and when the old workbook becomes read-only. Prepare a backup and rollback conditions before switching.
Before the switch, also agree how data can be exported and who maintains the application afterwards. Put these responsibilities alongside the acceptance criteria, so that the decision covers continued operation as well as the initial handover.
A decision worksheet to complete
Observe the same process over a period representative of your activity. Use this worksheet to document the decision, without a universal threshold or profitability score.
| Question | What to record |
|---|---|
| Frequency | Observed cases and incidents, with the period covered. |
| Time | Measured minutes spent copying, reconciling and correcting records. |
| Impact | Observed consequence: delay, corrected invoice or additional check. |
| Owner | Person making the decision and person resolving the incident. |
| Current control | Existing check and how an error is detected. |
In the hypothetical joinery example, follow one approved quotation through to production. Record manual transfers, document approval and prepare a cancellation case. Test that bounded workflow in the candidate solution before extending use. This scenario is not a Suniworks client case and promises no saving.
Where to start this week
Prepare a short decision note from the current workbook before drafting a feature list.
- Select the process whose corrections or manual transfers concern you most, and name its owner.
- Follow an actual record from arrival to completion, noting the people and tools involved.
- Document observed incidents, existing checks and rules that still need agreement.
- Use that same case to assess the alternatives, requesting demonstrations of the important exceptions.
Use the decision note to retain the workbook, improve it or prepare a bounded replacement. If an application is justified, Suniworks explains its approach to custom application development. Scope, acceptance and support commitments must be agreed for the particular project.