Inventory-First MS Access Migration Services

Move the file your team runs on to a secure web application, one workflow at a time.

Somewhere in your organization, a critical process runs on an Access database or an Excel workbook. It began as a quick fix and grew into the system the team relies on for scheduling, billing, referrals, inventory or reporting. It works, until a second person edits the same file, the person who built it leaves, or Microsoft stops supporting the version it runs on.

The risk is not the move to a web application. It is losing what the file quietly does: the forms staff use every day, the reports finance trusts, the macros and formulas that hold your business rules. Most migrations convert the tables and discover the rest later. Cabot lists every table, query, form, report, macro and formula first, ranks the workflows by risk, and then moves them one at a time.

Most engagements open with an inventory that produces an object map, a workflow ranking, a target design and a recommendation, which may be to rebuild as a web application, to move only the data to SQL Server or to leave the file alone. You decide before any build is funded.

Scope your project

Tell us what you run and when it has to move. An engineer replies within one business day, with no obligation.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

No obligation. Your details stay private.

What moving off MS Access actually involves

MS Access migration is the move of a database application built in Microsoft Access, or of a business process built in Excel, to a web application backed by a managed database such as SQL Server or PostgreSQL, with the data, screens, reports and business rules carried across and the old file retired once the new system has taken over.

Searches such as convert Access database to web application, MS Access to web and convert Excel to web app all point at the same need, but three different projects share the phrase. The first is Access to SQL Server, where the tables move to a managed database and Access stays as the front end. The second is Access to web application, where the data moves and the forms, reports and rules are rebuilt to run in a browser. The third is replacing the file with off the shelf software, which fits when your process is standard and does not fit when it is the way you differ.

The part most plans underestimate is what does not move on its own. Tables and relationships transfer cleanly. Forms, reports, macros and VBA code do not: Microsoft's own migration assistant for Access mainly migrates tables and simple queries. That is why we list every object first. Excel follows the same logic in a different shape. A workbook holds data, formulas, macros and a way of working all at once, so converting Excel to a web app means separating those four before rebuilding them.

A migration also does not mean every file should be replaced. A single user workbook with low stakes can stay as it is, and moving only the data to SQL Server is a legitimate place to stop. The inventory exists to tell you which situation you are in.

Why Access and Excel systems stall as the business grows

These are the six reasons operations and technology leaders give when a file that once saved time starts costing it. Most are not technical problems, and most stay hidden until something breaks.

Two colleagues reviewing records together at a laptop

The MS Access migration services we deliver

Six services, scoped to where you are. Some organizations need the full path from inventory to retiring the file. Others only need the data moved to a managed database, or have the data and need the screens rebuilt. We give you our recommendation and our reasoning before you commit to anything.

Each service produces something you can inspect: an object inventory, a workflow ranking, a running database, a working screen, a validated report. Testing and security run inside every service instead of sitting as separate lines.

What does an Access to web application migration cost, and what moves the number?

Five things set the cost: how many forms, reports and VBA modules the file holds, the volume and quality of the data, the number of users and roles, the integrations the new system needs and how long you want the old file and the new system to run side by side. A small database with a handful of forms and a sprawling one with years of macros are not comparable work, so any MS Access migration figure quoted before an inventory is a guess. Model a range in a few minutes, then tell us what you run and we will scope it properly. We would rather give you a narrow range you can plan around than a wide one that protects us.

Should you replace it at all? Four tests before you commit

Most disappointing MS Access migration projects were decided wrongly in the first week, when nobody asked whether a rebuild would help. These four tests come first, in a fixed order, and the honest answer is sometimes to leave the file as it is.

Test your own case: send us a short description of the file and we will tell you which of these four decides it for you.

What does AI actually change about moving off Access and Excel?

It changes the economics of the slow parts and leaves the judgment where it was. Reading VBA, macros and formulas that nobody documented, writing down in plain language what each one does, mapping which tables depend on which and finding orphaned queries are all work a model can draft quickly. Deciding which rules the business still needs, which were workarounds for old limits and whether a screen should exist at all is not.

In practice the saving concentrates in three places. Discovery goes faster, because a model can summarize an undocumented file into a list of rules and dependencies. Rebuilding goes faster, because the first draft of a screen, a report or a validation no longer starts from a blank page. Testing goes faster, because outputs from the old file become the expected results for the new system.

The risk runs the other way. A model can state a rule with confidence that a formula does not actually implement, so every documented rule is confirmed against real outputs and against the people who use the file before it counts.

So our process is built around review. AI shortens the slow parts of a migration. It does not decide which rules survive, approve a merge or sign off a cutover. Those stay with senior engineers and with you.

Three commitments hold on every engagement. Our process is model neutral, so we use the model your policy allows. A senior engineer reviews every change before it merges. And we never train any model on your code or data. Test data is synthetic or masked, so protected health information stays out of model prompts.

What we build the new system on, and what we build it with

Three layers of tooling, chosen against your environment and your team's ability to run the result rather than against our preferences. Hosting follows what you run today, or the platform our Azure consulting services and AWS cloud consulting services teams help you choose. We are platform neutral and recommend on evidence from the inventory. Our QA and testing practice builds the checks that compare the new system with the old file before anyone relies on it.

What we work in:

Data platform

SQL Server
PostgreSQL
Azure SQL Database
Amazon RDS
SQL Server Migration Assistant
Entity Framework

Application layer

.NET
C#
React
TypeScript
REST APIs
OpenAPI

Delivery and AI tooling

GitHub Actions
Docker
Playwright
SonarQube
GitHub Copilot
Azure DevOps

Where AI sits at each stage of the work, and where it does not

Each stage below has an output you can inspect and a person who approves it. Nothing an AI drafts reaches your data, your screens or your reports without a named engineer accepting it first.

Migration stage What AI does What stays human Tools used
Inventory Reads VBA, macros, queries and formulas and drafts a plain language list of the business rules they implement Confirming which rules still apply and which were workarounds for old limits GitHub Copilot, SonarQube
Data move Maps tables and relationships, flags orphan records and drafts migration scripts Approving the target schema and every data move SQL Server Migration Assistant, GitHub Copilot
Screens and rules Drafts the first version of forms, reports and validation from the documented rules Reviewing every screen and rule with the people who use them GitHub Copilot, TypeScript
Validation Compares outputs from the old file with the new system and summarizes the differences Accepting or rejecting each difference and approving each cutover Playwright, GitHub Actions

The last column names the tools, so a security reviewer can see exactly what touched the work. Where your policy limits which tools can be used, the same stages run with the tools you allow and the same human review.

How a Cabot migration differs from a typical Access conversion vendor's

Migrations succeed or fail on what happens to the forms, the rules and the cutover, not on whether the tables moved. Those are the places projects go wrong, so each row below is a moment where the approach changes the outcome.

Dimension Typical vendor Cabot
Starting point Begins converting tables Begins by listing every table, form, report, macro and formula
Forms and reports Rebuilt from screenshots or left behind Rebuilt from documented rules and checked against real outputs
VBA and macros Rewritten without a record of what they did Read, documented in plain language and confirmed with the people who own the process
Data target Whatever the vendor prefers SQL Server or PostgreSQL, chosen against your environment
Cutover A weekend switch One workflow at a time, with the old file still live
Rollback Restore from a backup The old file stays usable for each workflow until the new one has run clean
When they advise against it Rarely In writing, when the file is fine or moving only the data is enough
AI use Undisclosed or unreviewed Named tools, human review before merge, no training on your data

Ask any vendor when they would advise against replacing the file. A credible answer comes quickly and names the conditions. Ours is written into each assessment.

The organizations we migrate files and databases for

We deliver this MS Access migration work for three kinds of organization. Each card says what we understand about it, rather than claiming coverage of it.

Across all three the pattern is the same: the file is important enough that a failed cutover is not an option, and old enough that few people hold the whole picture. Where the new system exchanges clinical data, our healthcare integration services practice carries the same discipline into those connections.

Industries we already understand

volunteer_activism

Healthcare

shopping_cart

Ecommerce

paid

Fintech

apartment

Travel and Tourism

Client Success Stories

See all Cabot case studies

What a migrated system has to demonstrate before it goes live

Security leads every migration, because the move is your chance to fix what the file never had. We apply authentication, role based access, encryption in transit and at rest, an audit log of every change, automated backups with tested recovery and secrets held outside the code, and we keep protected health information out of test data and model prompts.

Where the system handles patient data, we map who can see what, scope the work to the safeguards your compliance team requires through our healthcare compliance services practice, and document each control the migration touches. For each workflow you receive evidence, not assurance: the comparison report from the parallel run, the list of changes with the engineer who approved each one and the plan for returning to the old file.

Role based access
Authentication and session control
Encryption in transit and at rest
Audit logging of every change
Automated backups and recovery
Secrets management
Synthetic and masked test data
HIPAA aligned controls
SOC 2 aligned controls

How an Access database or workbook becomes a web application

Six steps, each ending in a decision you make rather than a document you receive. Most engagements begin with the first two steps alone, so you can judge the plan and the working relationship before committing to the build.

Start with step 01: tell us what the file does and we will scope the first inventory.

Who migrates it, and what each person owns

Accountability is explicit from the first day. A solution architect owns the target design and the order of migration, and answers for choices that are expensive to reverse. A business analyst owns the documented rules and confirms them with the people who use the file. A data engineer owns the move to SQL Server or PostgreSQL and the checks that prove it. Senior full stack engineers own the screens and reports. A QA automation engineer owns the comparison between the old file and the new system. A delivery lead owns the schedule and tells you plainly when something slips.

Readers who search for an Access database developer usually need one person to patch a file. This team exists for the opposite reason: to remove the single person the file depends on, so the knowledge sits in documentation, tests and a team, not in one head.

Our depth is greatest in four places: reading VBA and macros nobody documented, moving Access data to SQL Server without losing integrity, rebuilding reports so finance trusts them again, and running old and new side by side to prove they match.

Your people join our standups and reviews from week one, so the knowledge stays with you. Where a larger group fits, we staff an embedded engineering pod inside your delivery cadence.

Why healthcare technology leaders choose Cabot for inventory-first MS Access migration

An MS Access migration is easy to start and hard to finish well. These are the six reasons buyers give when they explain why the work sits with us.

Where to go next, depending on what is in your way

Moving off a file is one part of the picture. What you need alongside it depends on which of these describes your situation, and it is usually one of three.

Our Clients

Questions operations and technology leaders ask before starting

  1. How do you migrate an MS Access database to a web application?
    Start by listing every table, query, form, report, macro and VBA module, and write down the business rules each holds. Then rank the workflows, move the data to SQL Server or PostgreSQL, rebuild the screens and reports as a web application with roles and an audit log, and run the old file and the new system side by side. Each workflow cuts over once it has run clean, and the file is retired last. Tables transfer cleanly, but forms, reports, macros and VBA must be rebuilt, which is why the inventory comes first.
  2. Can you convert an Excel spreadsheet to a web app?
    Yes, and the work starts by separating four things a workbook mixes together: the data, the formulas, the macros and the way people use it. The data moves to a database, the formulas become tested rules, the macros become workflow, and the way people work decides the screens. We confirm each rule against real outputs from the workbook, so the web app returns the same answers before anyone relies on it. A small, low stakes workbook may not need this, and we say so.
  3. Should we move Access to SQL Server only, or rebuild the whole application?
    Move only the data when the problem is size, corruption or users colliding and the forms and reports still serve you. Rebuild when the problem is access, auditability, remote use or rules that have outgrown the screens. Many organizations do both in sequence: the data moves first as a fast win, and the screens follow workflow by workflow. The inventory tells you which case you are in.
  4. What happens to my Access forms, reports and VBA code?
    They are rebuilt, not converted. Microsoft's own migration assistant for Access mainly migrates tables and simple queries, so forms, reports, macros and VBA need a deliberate approach. We read each one, document what it does in plain language, confirm the rule with the people who use it and rebuild it in the new system. Rules that were only workarounds for old limits are dropped, which is often where the new system gets simpler.
  5. How long does an Access migration take?
    It depends on the number of forms, reports and macros, the quality of the data, the number of users and roles and the integrations needed. Moving the data alone can take weeks. A full rebuild runs workflow by workflow over months, and the old file keeps working throughout. We give you a range after the inventory, so you see a timeline before you commit.
  6. How much does an Access migration cost?
    Cost follows the same drivers as the timeline: the volume of forms, reports and VBA, data quality, users and roles, integrations and how long the old and new run side by side. We give a range after the inventory, so you see numbers before you commit. For a first view, use the cost calculator.
  7. Is Access still supported by Microsoft?
    Access continues as part of Microsoft 365, but older versions have lost support. Microsoft ended support for Access 2016 and 2019 on October 14, 2025, and for Access LTSC 2021 on October 13, 2026, which means no more security fixes or technical support for those versions. Check which version your file runs on. A supported version does not remove the limits on size, users and auditability that drive most migrations.
  8. Can we keep using the old file while we migrate?
    Yes. The file keeps serving production while each workflow is rebuilt, tested and compared beside it. We move one workflow at a time, and the old file stays usable for any workflow that has not yet run clean in the new system. Where a short freeze cannot be avoided, usually for the final data cutover, we plan it with you for your quietest period.