Software Strategy
From Excel to a Custom Business System: When and How to Migrate
Moving out of Excel is a workflow and data decision. Start with the task that has become unreliable, then decide whether to improve the workbook, adopt an existing product or build a focused system. A small, checked migration is easier to evaluate than replacing every spreadsheet at once.

Section 01
When the workflow needs more than a workbook
Keep Excel when a workbook has a clear owner, manageable edits and reliable outputs. A migration deserves review when the same records are copied between files, staff cannot tell which version is current, or approvals and access rules are difficult to maintain. Document the actual failure before selecting a replacement.
A spreadsheet problem does not automatically require custom software. Compare improving the workbook, configuring an existing application and building a focused system. Test the required task in each realistic option. The choice depends on workflow fit, migration effort, access and ongoing ownership.
Section 02
Start with one process and a source register
Choose a bounded workflow, such as recording maintenance requests from receipt to assignment and completion. List the workbooks, sheets, attachments and manual steps that feed it. Identify who can decide which source is authoritative when files disagree.
Define what users must be able to do in the first release. Recording a request, assigning an owner and finding its history can be a useful scope. Adding accounting, inventory and customer portals at the same time changes the project substantially. Keep optional work visible for a later decision.
Section 03
Map the records before importing rows
Microsoft’s database-design guidance explains how records, fields, keys and relationships organize information. For a proposed migration, use that vocabulary to distinguish a customer, a property and a request instead of treating every worksheet row as the same kind of record.
Write a mapping for each field: its source, target, expected format and treatment when missing or conflicting. Decide how identifiers will be assigned and preserved. Names alone are usually an ambiguous matching rule; have the business owner resolve uncertain matches before they become accepted records.
Section 04
Test a small, representative import
Microsoft distinguishes importing a copy from linking to a source workbook. Confirm which behavior your proposed tool actually supports, and how later changes will be handled. Do not assume an import also transfers formulas, macros, validation rules or a live connection.
Use approved sample data to test ordinary rows and exceptions: missing values, repeated identifiers, leading zeros, dates and related records. Compare counts by record type, inspect the transformed values and resolve rejected rows. A matching total alone does not prove the records are correct.
Section 05
Example: a maintenance-request migration worksheet
This fictional planning example is not a delivered CARRAS project. Suppose a team uses one sheet for properties and another for requests. The first release needs to preserve the correct property relationship and give each open request an owner.
| Source | Target / rule | Check |
|---|---|---|
| Property code | Preserve a unique property reference | Every imported request points to the intended property |
| Request number | Use a stable request identifier | Repeated imports do not create a second request |
| Status / assignee | Map approved values and active users | Each open request has a valid status and owner |
| Dates / notes | Define date format and retain needed history | Inspect sample values and text after import |
Section 06
Agree on the switch, recovery and responsibilities
Before switching, decide when the old workbook stops receiving edits, who approves the final import and how changes made during the transition are captured. Keep a controlled source copy and document how to resume the previous process if acceptance fails. Avoid two independently editable sources without a reconciliation rule.
Test the agreed roles, sample tasks, history, exports and recovery procedure before approval. Assign responsibility for user access, support, backups and later changes. Microsoft’s cloud guidance is a useful reminder that the business retains responsibilities for its data and identities even when a provider runs infrastructure.
Section 07
What to bring to a migration review
Bring a description of the workflow, a sanitized sample structure, record counts, user roles, connected tools and the reports the business needs. Identify an internal owner and the first task that must work. Leave passwords and private customer records out of an initial public inquiry.
Carras Technologies can assess an existing tool, integration or custom internal system around that scope. The proposal should separate data preparation, implementation, migration, training and ongoing operation so the team can evaluate the full decision.