How to Move a Microsoft Access Database to a Web App

What Does Moving an Access Database to a Web App Involve?

It involves two jobs that are easy to mistake for one. The first is the data: tables, relationships and years of records move into a server database such as PostgreSQL, and that part is mostly scripted. The second is the application: every form, report, query and VBA routine your staff rely on becomes a screen, an export or a tested rule. That part is a rebuild, not a conversion.

PINCLER is an AI-first custom software development studio. We build data migrations, legacy rebuilds, back-office panels and other internal tools at a fixed price between $500 and $2,500, with the code, database and cloud account in the client's name. That is one of five routes open to an Access user; the table compares what each one changes, what it costs and when it fits.

Is Microsoft Access Still Supported After October 2026?

Only the newer versions are; the table shows the dates on Microsoft's lifecycle pages. To see which version you have, open Access and go to File > Account.

End of support does not switch anything off. The database still opens and the forms still run; what stops, according to Microsoft's Office upgrade guide, is technical support, bug fixes and security fixes. For a file that never leaves one office PC, that is a slow-moving risk. For a file staff open over a VPN or sync through a shared folder, it is a reason to plan.

Check what sits underneath, too. If your Access front end links to tables on SQL Server 2016, Microsoft's lifecycle page shows its extended support ending in July 2026, with Extended Security Update years listed to July 2029; if the shared .accdb sits on Windows Server 2016, that support ends in January 2027. None of these dates forces a move this month.

Which Signs Show Your Access Database Has Outgrown the Desktop?

Size and age are not the signs; how the file is used is. Microsoft's specifications put the limit at 2 GB per .accdb file, minus the space system objects need, and 255 concurrent users, figures most small databases never approach. Problems start well before either, when several people, places or devices depend on one file. Use the table as a self-audit before you pay anyone.

If your database is really a workbook with several tabs, moving off spreadsheets is the closer guide; this one assumes real Access tables, queries, forms and VBA.

What Happens to Your Tables, Queries, Forms, Reports and VBA?

Tables are data, and data moves by script. Forms, reports and VBA are an application. Commercial converters exist, but their output still needs engineering work, so plan the application as a rebuild. Microsoft's own tool shows where the line falls: SQL Server Migration Assistant for Access moves tables and data to SQL Server or Azure SQL, and its preparation guide says that afterwards you either keep using Access through linked tables or migrate the application by hand. That suits an office keeping its Access screens, but it puts nothing in a browser.

Expect to throw a lot away. Kolonell, a remote web studio, wrote in its Berlin cost guide of 6 October 2026 that in most audited Access databases, 30–40% of queries and reports are no longer used. Every object you retire is one less screen to build and test.

Most reports exist to be printed or emailed, and they become filtered screens with an Excel export. The few that must look exactly right, such as invoices or certificates, become PDFs generated from the data, a $500–$1,200 build quoted at 3–8 days.

What Is a Safe 10-Step Plan for an Access Migration?

Work through it in this order. The first four steps cost almost nothing and make every later step cheaper; the last three stop a migration from losing data quietly. Each step leaves something you can check.

Step 4 borrows Microsoft's list of Access features that cause trouble on the way to SQL Server, a good checklist for any target: a table with no unique index, for example, cannot be edited after Microsoft's tool moves it. For step 8, see how to test software before launch.

1. Back up the .accdb and freeze design changes; Microsoft's guide also advises backing up the target and documenting the source.
2. Inventory every table, query, form, report, macro and module, with an owner for each. Access's Database Documenter gives the raw list.
3. Retire what nobody has used for a year, after checking with its owner.
4. Fix tables without a primary key or unique index, relationships to them, names that are SQL keywords or contain special characters, key fields of different sizes, and Access functions in validation rules.
5. Profile the data: duplicate customers, dates stored as text, mixed phone formats and, for SQL Server targets, dates before 1 January 1753.
6. Agree the field mapping in writing: each source column, its target and its cleaning rule.
7. Build the new database and a repeatable import script, so the move can be rerun.
8. Rebuild the most-used workflow first, with one automated test for each VBA rule it replaces.
9. Do a full dry run with a reconciliation report of record counts and totals.
10. Run old and new side by side, cut over in a quiet week, and keep the .accdb read-only as an archive.

Should You Upgrade Access, Use Power Apps or Build a Web App?

Decide by who uses the database and from where, not by how old it is. The tree carries no price on purpose; the arithmetic follows it.

For a ten-person team over three years: at the time of writing (October 2026), Microsoft's Power Apps pricing page lists Premium at $20 per user per month, paid yearly, and says prices vary by region. Ten users cost $20 × 10 × 12 = $2,400 a year, or $7,200 over three years.

A custom build is one payment per phase, then hosting. One phase of a legacy rebuild is advertised at $1,500–$2,500. For hosting, at the time of writing Supabase's pricing page lists its Pro plan from $25 a month, $900 over three years, as one example of managed PostgreSQL. For a database that fits one phase, that comes to roughly $2,400–$3,400 over three years with no per-user licence. A migration can need two or three builds (see the next section), and each extra phase adds its own fixed price: three full $2,500 phases plus hosting come to $8,400, more than the licences.

Add maintenance on top: PINCLER's optional care plans start at $99 a month, or your own developer can take over. The Power Apps figure is licences only; building the apps and moving the data cost extra there too. Kolonell's guide estimates a Berlin rebuild at EUR 20,000–50,000 excluding VAT plus EUR 3,000–5,000 a year for maintenance, though it prices a whole application rather than one phase.

Power Apps is still a fair choice for a team deep in Microsoft 365 with someone in-house to build and look after the apps. A custom build fits better when headcount will grow, when the rules need automated tests, or when nobody would own a low-code app after its builder moves on. No-code versus custom development covers the general trade-off.

Does more than one person edit the database?
  NO  -> Is it on a supported Access version?
           YES -> keep it; back it up nightly
           NO  -> upgrade Access and stop here
  YES -> Do people need it from home, on phones
         or with customers?
           NO  -> upgrade Access; move the tables
                  to a server database if the
                  file struggles
           YES -> Is there one main workflow?
                    YES -> one-workflow web app
                    NO  -> phased rebuild, one
                           module at a time

How Much Does an Access Migration Cost, and How Long Does It Take?

Each part of the move maps to a build in PINCLER's published catalogue. A migration can combine two or three of them, each run as a separate fixed-price phase, and none goes above $2,500 a phase, because AI drafts the scripts, screens and tests and senior engineers review, test and harden them.

The data migration and cleanup build names an old Access database moving to PostgreSQL among its examples; its tiers are a $600 single-source move, a $1,100 cleanup migration with deduplication and a signed-off dry run, and a $1,800 multi-source merge. A database built around one workflow follows the spreadsheet-to-web-app pattern: one core table rebuilt with forms, roles, change history and exports, from $800, or $1,400 with every historical row imported.

Several connected modules and years of VBA call for legacy app modernisation, in phases of $1,500–$2,500 over 16–28 days. Its tiers: Inventory and first module at $1,500; Core rebuild at $2,000, with two or three modules, role-based access, audit logs and a reconciliation report; and Full phase at $2,500, adding mobile-friendly screens, side-by-side running and automated tests.

Cloud deployment and CI/CD puts the server and pipeline in your accounts. Kolonell's guide plans three to five months for a Berlin rebuild; AI drafting and a smaller first phase make the difference, while the review, tests and reconciliation stay. Every quote sits inside the fixed pricing bands.

Who Should Move Off Access Now, and When Is Upgrading Access Enough?

Move now if the database has become shared infrastructure: several people edit it at once, staff need it outside the office, customers would benefit from their own access, or the business depends on one person who understands the VBA. Then a corrupted file or a resignation costs more than a fixed-price phase.

Upgrading Access is enough when one person, or a small team in one office, uses a database that works: move to a supported version, schedule backups and Compact and Repair, and spend the money elsewhere. Do not build a web app for a database you will retire within a year, or when nobody on your side will own the new system.

• Good fit: a shared .accdb that several staff edit at once over the network.
• Good fit: staff who need the data from home, on site or on a phone.
• Good fit: VBA that only one person understands or dares to change.
• Good fit: customers or suppliers who keep asking for data you send by email.
• Poor fit: a single user on one PC with a database that works.
• Poor fit: a database due to be retired or replaced by a packaged product within a year.
• Poor fit: no one on your side to own the new app after launch.

What Are the Most Common Mistakes When Migrating From Access?

Access migrations rarely fail on code. They fail on scope, data or people, and each mistake below can be avoided before work starts. One rule covers several: keep the repository, database and hosting account in your company's name from day one, and who owns your code lists what to check. Kolonell's guide names three of these mistakes: rebuilding everything, neglecting the data and sidelining the database's keeper.

1. Rebuilding every query and report. Retire the unused ones first; the inventory usually finds plenty.
2. Leaving out the person who built the database. That person knows the rules the VBA never wrote down.
3. Cutting over in one go. Run old and new side by side until the reconciliation report matches.
4. Skipping the data profile in step 5, so mixed phone formats or pre-1753 dates bound for SQL Server surface at the dry run instead of before it.
5. Copying old screens one to one. Fix the workflow, but keep the field names staff already use.
6. Deleting the .accdb after go-live. Keep it read-only; it is your evidence if a number is questioned.

PINCLER's Perspective on Access Migrations

Access migrations suit the way PINCLER works. The rules already exist in the forms, queries and VBA, so AI tools can read them and draft the schema, import scripts, screens and one test per rule. Senior engineers decide what to keep, design the roles, check every reconciliation and own the cut-over.

Across the 79 builds in PINCLER's published fixed-price catalogue, the median advertised price is $1,450 and the median quoted delivery 13 days. The six internal-tools builds have a median of $1,725 and 16 days. The four data builds, which include the migration build, have a median of $1,100 and 9 days, indicative only with so few records. That is a published price list rather than a delivery record, set out in what you can build.

Every phase follows the same build process: a free call, a one-page fixed-price scope within a working day, an early preview, senior review and hardening, and handover with the code, database and cloud accounts in your name. A database with dozens of forms and years of VBA does not fit one phase; we split it into phases by module, each within the band, or decline it. Software maintenance costs covers the patch-or-rebuild arithmetic, and internal tools on a small-business budget covers what an Access database often becomes.

The Bottom Line

Moving an Access database to a web app is two jobs: a scripted data move that is easy to verify, and a rebuild of the forms, reports and VBA that deserves most of the care. Done in phases, it costs $600–$2,500 a phase at PINCLER, because AI drafts the scripts, screens and tests and senior engineers review, test and harden them.

If one person uses the database on one PC, upgrade Access and keep it. If several people, places or devices depend on it, run the self-audit table above and bring the result to us: a free 30-minute call returns a written fixed quote within a working day, and the legacy app modernisation page shows what a phase contains.