Blog

Moving from Excel to an application, step by step, without stopping work

The most common reason businesses keep an overgrown spreadsheet is not cost. It is fear: "Everything we have is in that file. What if something goes wrong during the switch?"

The fear is reasonable, and the answer to it is a method. A system the business runs on is never replaced in one jump. Here is how we do it, in six steps.

1. Understand what the old system really does

Every long-lived spreadsheet or Access database does more than its owner remembers. There are formulas someone added in 2016, a macro that runs at month end, a hidden sheet a report depends on.

So the first step is to sit down with the person who uses the file most and go through a normal working day and a month-end. The result is a short list: what goes in, what comes out, which rules apply. This is also the moment to drop what nobody uses any more.

2. Agree on a small, clear specification

The new system should do what the old one does, minus the workarounds. That fits on a few pages: screens, reports, user roles and rules. You approve it together with a fixed price, before any building starts.

3. Build in stages, with a demo each time

Instead of disappearing for two months, the work is delivered in parts: first data entry, then lists and search, then reports. After each part you click through a working version and say what is missing. Misunderstandings cost an hour to fix at this point, not a week.

4. Move the data, on a copy first

Data migration is where care matters most. The old data is exported, cleaned (duplicates, inconsistent names, empty fields) and imported into the new system, first as a trial run on a copy.

Then the totals are compared: number of customers, number of invoices, sums by month. The trial is repeated until the two systems agree.

5. Run both side by side

For a short period, often one or two weeks, the old and the new system run in parallel. Staff do the real work in the new one, while the old one stays available for comparison. Nothing is switched off until the people who use it say it is ready.

6. Switch over, train and keep the old file

On an agreed day the final migration is done and the new system becomes the only one. Staff get a one-page guide and a short training session. The old file is kept, read-only, as an archive. Knowing it is still there makes the first weeks much calmer.

What makes the difference

  • The old system keeps working until the new one is approved, so the business never stops.
  • Every stage can be checked by the people who know the job.
  • The data is verified with numbers, not by trusting that the import "probably worked".

If your company runs on a file like this, you can read more about how we rebuild old systems, or send us the file for a free review and we will tell you what a switch would involve.

← All articles

Want us to look at your system?

Send us your file or describe the problem. You get three concrete suggestions within 48 hours.