Access or Excel to Quickbase Migration

Why businesses finally leave Access and Excel

Nobody migrates off a working system for fun. The Access and Excel replacements I have done all started the same way: a system that ran the business faithfully for ten or fifteen years hit a wall, and the wall was usually a person, not the software.

Two real examples, anonymised. A distributor of cleaning products ran its pricing and order operations through an Access-based ERP built years earlier. It worked, but only a couple of people understood its internals, pricing logic lived partly in code and partly in heads, and every change was a risk nobody wanted to take. We replaced it with a Quickbase pricing engine. Separately, an environmental services firm ran its core records in an Access database that had outgrown multi-user desktop life: locking conflicts, no useful remote access, and a growing fear of the file corrupting. Same pattern, different industry.

The common triggers, in the order I usually hear them:

• The person who built or understood the database has left, retired, or wants to
• Multiple staff need simultaneous access, and Access file-sharing is straining or corrupting
• The business needs web and mobile access, which desktop Access was never built for
• Excel has splintered into fifteen versions of the master file and nobody trusts any of them
• An owner realises the system is a due diligence problem: a buyer cannot verify a business that runs on one person's database

All of these are versions of the same fault: critical operations depending on a fragile artefact and the memory of whoever maintains it. The migration is really an owner-dependence removal project wearing a software costume.

What migrates cleanly, and what has to be rebuilt

Set expectations correctly at the start: this is a rebuild that reuses your data, not a lift-and-shift. Here is how the pieces divide.

Migrates cleanly:

• Tables and data. Access tables and Excel sheets export to CSV and import into Quickbase tables directly. This is the easy 40 percent.
• Relationships. Access relationships between tables map naturally onto Quickbase table-to-table relationships. They are rebuilt rather than imported, but the design transfers almost one for one.
• Most calculated logic. Excel formulas and Access calculated fields usually translate to Quickbase formula fields without drama.

Gets rebuilt, not moved:

• Forms. Quickbase generates default forms which you then shape. Your old Access form layouts do not transfer, and mostly should not: many exist to work around limitations the new platform does not have.
• Queries and reports. The intent maps well onto Quickbase reports, but each one is recreated. This is a good moment to discover which of your 60 saved queries anyone still uses. In my experience it is about a dozen.
• VBA, macros, and code. None of it ports. Every piece of logic gets one of three fates: replaced by a native Quickbase feature, rebuilt as a formula or pipeline, or deliberately dropped. In the distributor project, a large share of the VBA existed to do things Quickbase does natively, so the rebuilt system had far less logic to maintain than the original.

The rule of thumb: data transfers, structure translates, behaviour gets rebuilt. Pricing a migration as a data copy is how projects end up at double their quote.

The data cleanup step everyone underestimates

In every migration I have run, data cleanup took about a third of the total effort, and every client was surprised. A database that has run for a decade accumulates sediment, and the old system hid it because the people using it knew which records to ignore.

What we reliably find:

• Duplicates. The same customer entered three ways over ten years. Access and Excel enforce very little, so nothing stopped it.
• Orphaned records. Order lines pointing at deleted products, jobs pointing at customers who no longer exist. Quickbase's relationships will refuse this data, which is a feature, but it means the mess must be resolved before import.
• Meaning stored in formatting. Excel is the worst offender: rows coloured yellow mean on hold, bold means priority, and none of it survives a CSV export. That meaning has to become actual fields.
• Inconsistent codes and dates as text. Three formats for the same product code, dates that sort alphabetically. All standardised before import or the reports lie forever.
• Undocumented rules. The biggest one. In the cleaning-products project, extracting and verifying the real pricing rules, which lived partly in VBA and partly in two people's heads, took longer than building the pricing engine that replaced them. The build was straightforward once we actually knew the rules.

Clean before you import, not after. Fixing data inside the new system while staff are already using it is slower, riskier, and demoralising. This is exactly the work of a Data Readiness Sprint, from $6,000 plus GST over 2 to 6 weeks, and on a migration it is usually the best-spent money in the project.

Realistic timelines and what it costs

A typical single-application migration from Access or Excel to Quickbase runs 4 to 10 weeks end to end. Simple Excel-based processes land at the short end. A multi-table Access system with embedded logic, like an old ERP, sits at the long end or beyond, and is usually better done in phases.

The sequence that works:

1. Scope, 1 week. Map the tables, the relationships, the logic, and crucially who uses what. The Business Readiness Audit covers this for $1,990 inc GST, fixed scope with written findings, credited toward the engagement within 90 days.
2. Data cleanup, 2 to 6 weeks. As above. Can overlap with early build once the structure is settled.
3. Build, 2 to 5 weeks. Tables, relationships, forms, reports, automations, permissions. Typical cost $8,000 to $25,000 plus GST depending on how much logic gets rebuilt.
4. Parallel run, 2 to 4 weeks. Both systems live, reconciling record counts and key totals weekly until they agree and staff trust the new one.

On the environmental services project, we phased it: the core register moved first, staff got confident, and secondary modules followed. That beat a big-bang cutover on every dimension except impatience.

Add the Quickbase licence itself, which at the time of writing starts around USD 35 per user per month billed annually with a 20-user minimum, roughly A$13,000 a year at recent rates. For a business leaving a system that only one person can maintain, that cost buys something Access never offered: a platform that does not depend on a single irreplaceable file or a single irreplaceable person.

How to cut over without breaking the business

Migrations fail at cutover more often than at build. The system was fine; the transition was botched. The rules that prevent that:

• Run in parallel, and actually reconcile. For two to four weeks, both systems operate and someone compares record counts, totals, and a sample of individual records weekly. Trust is built by agreement between the systems, not by assurances.
• Freeze the old system to read-only at cutover. The single worst outcome is staff quietly continuing in Access because it is familiar, splitting your truth across two systems. Read-only access preserves history while making the new system the only place work can happen.
• Keep the Access file or spreadsheets as an archive. Do not delete history. You will want to check an old record within a month, guaranteed.
• Train on real work, not demos. An hour of staff entering their actual current jobs into the new system beats three hours of slides. Resistance drops the moment the new form is faster than the old one.
• Do not migrate every module at once. Move the core process, stabilise, then follow with the rest. Each phase de-risks the next.

If your business is running on an ageing Access database or a spreadsheet only one person truly understands, the honest first step is finding out what a migration would actually involve for your specific data. The Business Readiness Audit does that: $1,990 inc GST, fixed scope, written findings on your data, your logic, and a costed migration path, fully credited toward any engagement within 90 days. It is a small price to stop guessing about the thing your business runs on.

FAQ

Questions owners ask