It's 9:40 on Monday and
Order_Tracking_v7_FINAL.xlsmis open on Marcela's computer. Nobody else can save changes until she closes it. On Friday someone deleted a formula in the discount column and 40 quotes went out with the wrong price. The macro that builds the weekly report was written by an analyst who left two years ago.
Almost every company has a process like this. It started as a handy spreadsheet, picked up macros over time, sometimes ended up in an Access database, and now operations depend on it even though nobody ever designed it as a system. When does it make sense to move to custom software development? When keeping the spreadsheet alive starts to cost more than replacing it. This article covers how to spot that moment, what it takes to replace Excel macros or migrate Access to a web app, and how to make the switch without stopping the business.
Signs the spreadsheet has hit its limit
Excel and Access are good tools to start with. You can test an idea in a few days without asking anyone for anything, and often that's the right call. Trouble starts when the file becomes the central system for a whole team. Watch for these:
- Several people need to work at the same time. Files with VBA macros don't handle simultaneous work well: Excel for the web lets you open and edit a macro-enabled workbook, but you can't run or edit the macros there. The process stays tied to whoever has the desktop version open.
- Competing copies. "The good version" lives in someone's inbox, on a shared drive and on a USB stick, each with different data.
- Nobody knows who changed what. If a number is wrong, there's no way to tell who touched it or when. In a process that handles money, inventory or customer data, that's an internal control problem.
- Only one person understands the logic. If they leave or get sick, the process stalls.
- Errors show up late. Overwritten formulas, rows pasted out of range, dates stored as text. The spreadsheet validates nothing you didn't explicitly program.
- Macros start running into security. Microsoft blocks macros by default in files that come from the internet, email attachments included. It's a sensible policy, but in practice it means asking IT for exceptions or teaching people to unblock files, which is exactly the habit you want to avoid.
If you see three or more of these in the same process, it's worth evaluating a change.
The technical limits, specifically
Most companies hit the operational limit long before the technical one. Still, it helps to have the numbers handy:
| Tool | Documented limit | What it means in practice |
|---|---|---|
| Excel (.xlsx) | 1,048,576 rows by 16,384 columns per sheet | Plenty for most uses, but a large file full of formulas and macros slows down well before that |
| Excel (.xls, legacy format) | 65,536 rows per sheet | Legacy files in this format are still around |
| Access (.accdb / .mdb) | 2 GB per database, objects and data combined | Near the limit you end up splitting the database or compacting it constantly |
| Access, concurrent use | Up to 255 simultaneous users, per Microsoft | On a network share, locking issues and corrupted files tend to show up with far fewer users |
These numbers are rarely the reason to migrate. Usually the process just can't be controlled anymore: who gets in, who edits, what happens when something breaks.
What changes with a web application
In a spreadsheet, data, rules and screens are all mixed into the same file. A custom web application pulls them apart.
The data moves to a relational database such as MySQL or SQL Server. Every field has a defined type (a date is a date, an amount is a number) and the database enforces relationships on its own. You can no longer enter an order for a customer that doesn't exist.
The rules that now live in formulas and macros become server-side code. The discount calculation sits in one place, with tests, and nobody can wipe it out by accident from a cell.
The screen is a browser form built for each role. Sales reps see their quotes, the sales manager approves discounts, and finance sees everything without being able to change prices.
That gets you things a spreadsheet struggles to deliver:
- Many people working at once without the file locking up.
- Role-based permissions and a log of who changed what.
- Automatic database backups instead of manual copies.
- Access from any device with nothing to install.
- Connections to other systems, like your ERP, through APIs. If that's your situation, see our article on integrating systems with your ERP and banks.
There's also a legal angle in Chile. If the spreadsheet holds personal data about customers or employees, Law 21,719 requires security measures proportional to the risk. Its effective date is currently set for December 1, 2026; a bill in Congress to postpone it was still moving through the legislative process in early November, according to Eguiguren Abogados' tracker. Whatever the final date, it's hard to show access control over a file that keeps getting forwarded by email.
How to migrate without stopping operations
The most common mistake is copying the spreadsheet as is, cell by cell. A migration is a good excuse to understand the process and drop what's no longer needed. A sensible path:
- Inventory the file: sheets, macros, important formulas, Access queries, external connections and who uses each part. It's common to find that half the sheets haven't been opened in ages.
- Talk to the users. The spreadsheet shows what gets done; people explain why. That's where the undocumented exceptions come out ("customers outside Santiago get a different freight rate").
- Data model: tables, relationships and validation rules. Of all the steps, this one has the biggest effect on the quality of the final system.
- Clean and load the data. Duplicates, the same customer spelled three ways, dates as text. Run a test load early to see how messy things really are.
- Prototype and build in stages. Users click through the screens before they're built, then get partial releases to test.
- Run in parallel, then cut over. For a few weeks the app and the spreadsheet can run side by side so you can compare results. After that the file goes read-only and gets archived.
If you're putting together a brief to get quotes, our guide on writing a software development requirements brief may help.
Custom code or low-code?
Not everything that leaves Excel needs code from scratch. For a simple flow inside Microsoft 365, like a request with an approval step and an email notification, Power Apps with Power Automate may be enough. Custom development makes sense when there are complex business rules, many users, outside users (customers or suppliers) who need access, or integrations with several systems. We compare both paths in more detail in low-code or code.
Frequently asked questions
Can the VBA macros be reused in the web app?
Not directly. VBA runs inside Excel or Access and doesn't work on a web server. What you can reuse is the logic: the macros work as a specification of what the new system must do, and it's worth going through them line by line before rewriting them.
What happens to the spreadsheet's historical data?
It gets cleaned and loaded into the new database. If the history is very long or very messy, you can migrate only the years people actually look up and keep the rest archived as read-only.
How long does it take to migrate Access to the web?
It depends on how many tables, forms, reports and integrations there are, and on the state of the data. A contained process for one team can be done in weeks; one that spans several teams or systems takes longer. The real timeline comes out of a review of the file and the process.
Make the move with a plan
At Disrupsoft we build web applications and internal systems for companies that have outgrown their spreadsheets, using technologies like Angular, Node.js, Symfony, MySQL and Azure. We start with a review of your process, show you a clickable prototype and build in stages, with releases every two weeks. If an Excel file with macros or an Access database is holding up something critical, tell us about it and we'll figure out where to start together.



