Service · Web development

Replace your Microsoft Access database with a modern web platform.

An Access application that worked perfectly well for years eventually grinds to a halt: nobody dares touch it, only one colleague understands the macros, it doesn't work on mobile, and its GDPR position is weak. We migrate your .mdb or .accdb to a scalable web app with multi-user access, an audit trail and a proper back end.

Data exportForms to web UIReports to BIGDPR-compliantAudit trail

Access was once the smartest choice. Until it wasn't.

For decades, Microsoft Access has been the pragmatic answer for SME administrations, accountancy firms, local government, small healthcare practices, lab environments and production tracking. Someone with domain knowledge built a working application without a developer: tables, forms, queries, reports and a few macros, all in a single file. In many organisations that Access application is still running, because it "just works".

The problem is that "just works" is deceptive. An .mdb or .accdb sits on a network drive, sometimes on a file share from the Windows Server 2008 era. With one user it's fine; with two you get a record-lock issue; with five you get a corrupt file that has to be backed up in the evening and restored in the morning. There's no mobile app, no audit trail, no role management beyond a password on the file, and logic in VBA macros that exactly one person can still decipher.

Replacing an Access database is therefore rarely a technical luxury project. It is usually a combination of risk management (GDPR, audit, single point of knowledge), scalability (more users, mobile access) and further development (your work process has evolved beyond what Access can handle). Our approach fits within our broader practice in web development and is closely linked to the wider context of platform migration: an Access migration is at heart a platform migration with Access-specific pitfalls.

Three flavours of replacement.

Not every Access database calls for the same approach. Sometimes the existing logic is so specific to your business that a custom build is the only right route. Sometimes the work process has become generic enough that a low-code platform will do. Often it's a hybrid: the core custom-built, the edges low-code.

Compact project · fixed sprint budget

Low-code replacement (PowerApps or AppSheet)

For relatively generic administrative applications, such as a member register, a small customer file, stock tracking or a simple forms flow, we convert your Access database to Microsoft PowerApps, AppSheet or a comparable low-code environment. The data moves to Dataverse, SQL Server or Google Cloud SQL; the Access forms are rebuilt in the low-code editor; reporting moves to Power BI or Looker Studio. A deliberate choice when your organisation needs to be able to adapt the solution itself without a developer.

PowerApps / AppSheetDataverse / SQL ServerPower BISharePoint integration
Mid-sized project · fixed sprint budget

Custom web app (Postgres + React)

For Access databases where your business logic lives, such as specific calculations, your own workflow or integrations with other systems, we build a custom web application. Data moves to Postgres, MySQL or SQL Server; forms are rebuilt in React, Vue or Astro as a single page application; queries are exposed as a REST or GraphQL API; macros are translated into clear back-end logic. Including multi-user support, an audit trail and role-based access.

Postgres / SQL ServerReact / Vue / AstroREST / GraphQLAudit log
Larger project · fixed sprint budget

Hybrid platform with data layer and BI

Where several Access files live side by side, often grown over the years with overlapping data and logic, we first consolidate the data layer (see also our page on data engineering platforms) and build a digital platform on top of it that takes over and extends the Access functionality. Suitable for organisations that want to use the migration to get their reporting and BI position in order at the same time.

Data warehouseETL / dbtPower BI / MetabaseSSO & role management

What you get at the end.

No more .accdb files on a network drive, no more VBA macros that only Jan understands, and no more «this file is in use by someone else» pop-ups. Instead, you get an environment you can manage yourself or have managed for you, with the data and logic fully in your own hands.

  • The new environment, in productionProduction and staging environments in your own cloud (Azure, GCP, AWS) or hosted by us. With daily backups, monitoring and a recovery procedure that has been tested.
  • Full data migrationAll records from your .mdb or .accdb transferred and validated against record counts, foreign keys restored where Access left them implicit, and a mapping document so it is clear which column ended up where.
  • Rebuilt forms and workflowsYour existing entry, edit and lookup screens rebuilt as a web UI, tested by your own end users in pilot sessions before the old environment is switched off.
  • Reports and BIYour Access reports converted to Power BI, Metabase or Looker Studio, with live data from the new database. No more manual Excel export for the monthly report.
  • API and integrationsQueries and data available through a clean REST or GraphQL API, with documentation. Ready for integrations with your accounting package, CRM or other systems via smart API integrations.
  • Full codebase and documentationSource code, build instructions, database schema, architecture overview and an incident runbook. No vendor lock-in: another team can take it over.
  • Training and ongoing managementSessions for key users plus short videos for end users. Optional management contract with monitoring, backups, security patches and further development at a fixed monthly price per tier.

When replacing Access is the right choice.

Five patterns in which organisations come to us to replace their Access environment. If you recognise one of them, a conversation is usually worthwhile, even if we end up concluding that a light upgrade is enough rather than a full replacement.

Single-user lock

Only one colleague can use it at a time

The Access application is supposed to be multi-user, but in practice the second user gets blocked. Records get locked, the file occasionally corrupts, and the IT team restores backups in the morning before the day can begin. As the team grows, this doesn't hold up.

No mobile access

Unusable outside the office

Your field staff, on-site employees or colleagues on a production floor have no access to the Access environment. They note everything down on paper or in Excel and retype it in the evening. A web environment solves that in one go: tablet, phone, laptop, all showing the same screen.

GDPR risk

Personal data stored locally

Your Access database contains personal data (customers, patients, employees, members) and sits as an .accdb file on a network drive with unclear access. Who has copies? Who changed what? In the event of a data breach or an investigation by the Dutch Data Protection Authority (AP), you are in a weak position. The GDPR requires demonstrable access control and logging.

Audit trail requirement

NEN 7510, Wta or compliance requires logging

If you work in healthcare, NEN 7510 requires demonstrable logging of who has seen and changed what. In accountancy and financial services, the Wta (Dutch Money Laundering and Terrorist Financing Prevention Act) applies, with similar requirements. Access doesn't offer that; a modern web app does as standard, with an immutable audit log for every record change.

Single point of knowledge

One person knows the macros

The Access application was built up over the years by a single colleague. VBA macros, complex queries, numerous form events. If that colleague retires, resigns or is off sick for a long time, nobody knows how the thing works. That is an operational risk that only reveals itself when it is already too late.

Development has stalled

New requirements no longer fit

You want to add a customer portal, a mobile scanner flow, an integration with your accounting software or support for multiple branches. In theory Access can still handle that, but every extension becomes a hack, and nobody can guarantee the old flows will keep working. Over the years the environment has become too heavy for the platform.

How an Access migration project runs.

1

Introduction and quick scan of your .accdb

An initial conversation in which we learn what the Access database is used for in your work process, how many users it has, and what pain points and wishes there are. We then run a short technical scan of the file itself: number of tables, relationships, forms, queries, reports and VBA macros. By the end you have a first sketch of the migration scope and an idea of the right target platform.

2

Discovery with your end users

A workshop with your team plus interviews with a few daily users: what do you do in Access now, what would you actually like to do, and which flows are business-critical? At the same time we carry out a thorough analysis of the Access file: reading out macros, walking through queries and mapping data relationships. By the end you have the scope, a plan, screen flows and the target platform for each component.

3

Data export and schema design

We export the data from your .mdb or .accdb to Postgres, MySQL or SQL Server. Foreign keys that Access left implicit are made explicit, column types are harmonised, and data quality is checked with a report of discrepancies. For running in parallel, we set up a synchronisation script so your people can keep working in Access for a while as the new environment is being built.

4

Building the web app in sprints

A working build every two weeks. We start with the most-used flow, usually one main form with its associated lookup queries, and expand in later sprints with the remaining forms, reports, audit trail and API integrations. Your key users test along the way. The macros are not translated one-to-one, but reworked into clear backend logic with tests.

5

Pilot, training and go-live

A pilot group works for two weeks in both the old Access database and the new environment. Differences are found and fixed, and screens are refined based on feedback. Then come training sessions for key users, short videos for end users, and go-live with a clear rollback procedure as a fallback. Access remains available read-only for a while for historical reference.

6

Further development and maintenance

An optional support contract with monitoring, backups, security patches and further development of requirements that fell out of scope during discovery. The environment grows with your work process.

The migration approach in detail.

Replacing an Access database breaks down into six tracks. First the data export: tables from the Access file are transferred to the target database (Postgres, MySQL or SQL Server, depending on what your IT environment already runs). Access-specific column types (AutoNumber, Yes/No, OLE Object, Hyperlink, Memo) are mapped to serial, boolean, bytea and text. Foreign keys that lived implicitly in Access (via lookups in forms) are made explicit in the schema with the corresponding constraints.

Then the forms. Access forms are often a mix of input fields, lookup comboboxes, sub-forms and VBA events. We rebuild them as a web UI in React, Vue or Astro, with the same fields and validation rules but in a design that works across multiple screen sizes. Sub-forms become tabs or accordions, lookup comboboxes become search fields with autocomplete, and validation happens in the browser and again on the server side.

The reports move to a BI environment: Power BI if you are Microsoft-oriented, Metabase for self-hosted, or Looker Studio for Google environments. The advantage: reports become live, shareable via a link and interactively filterable instead of compile-time. The monthly report that used to take an hour of Excel work becomes a dashboard that is always up to date.

The macros are the delicate part. VBA code can range from trivial ("clear this field on a new record") to complex ("generate an invoice PDF using multiple queries and email it to the customer"). We document every macro, decide with you which ones are still relevant to the new way of working, and rebuild them as backend logic in TypeScript or Python with tests, so that a later change doesn't quietly break a calculation. The rest we deliberately drop.

The queries, especially the saved queries used in forms and reports, become API endpoints. A REST or GraphQL API returns the data that used to come from a query result. That immediately opens the door to integrations with other systems: your accounting software, CRM, a mobile scanner app. Or another team can build its own customer portal on that API without having to touch the database itself.

Finally, the cut-over. Nobody likes switching over in one go without a safety net. We work in parallel: Access remains as a reference, and a synchronisation layer mirrors changes between old and new. At go-live the write direction switches; Access remains available for historical reference.

Sectors where Access is still widely used.

Microsoft Access survives in six types of organisation that we increasingly see as clients. SME administration: small businesses with their own customer or order database, often built at some point by one employee with an aptitude for IT. It works well for the first hundred customers and grinds to a halt at the thousandth.

Small healthcare practices: dentists, physiotherapists, small mental health organisations. Patient records, appointments and treatment history in an Access file, a setup that now conflicts with NEN 7510 and the GDPR. Replacement is often no longer optional here; auditors ask for demonstrable access control and an audit trail.

Accountancy and bookkeeping firms: small firms with their own Access database for hours, clients, files and invoice status, alongside their accounting package. The Wta requirements around file-building and audit trails have become stricter; Access generally doesn't meet them without a lot of manual work.

Local government and public services: municipal departments, water boards, small implementing organisations, often with a register, permit database or internal enforcement tool in Access. This is where the GDPR, Woo (Open Government Act) requests and inter-governmental information exchange come together.

Research, labs and R&D: university research groups, clinical labs and smaller R&D departments that track experiments, samples and measurements in Access. These often start with a PhD student; two years later the organisation is left with a knowledge vacuum. A web app with an API offers the added benefit here that data can land directly in a data pipeline.

Production tracking and small-scale manufacturing: SME manufacturers that keep their work orders, stock and quality checks in Access. The pain points here are mainly mobile (operators on the shop floor have no access) and integration (accounting, ERP and Access don't run in sync). Replacement is often combined here with a first integration layer towards integrations with other systems.

Technology choices we make along the way.

The target platform depends on two questions: how specific is your business logic, and how much ability to make changes yourself does your organisation want to keep? For generic administrative flows, a low-code route such as PowerApps with Dataverse or AppSheet with Google Workspace is a sensible choice. Your own people can make small changes later without a developer. The downside: the ecosystem sets the rules, so vendor lock-in is real.

For applications where your own logic lives, we choose custom. Postgres is our default database: open source, robust and widely supported. SQL Server if your IT team already works with it, MySQL in shared hosting scenarios. Front end in React, Vue or Astro; back end on Node.js, Python (Django or FastAPI) or .NET, depending on what your own or future maintenance partner knows.

For the migration itself, we use ODBC connections to the Access file, a Python script with pandas or a tool such as mdbtools to extract the data, and dbt or custom SQL scripts for the transformations to the new schema. For BI: Power BI (Microsoft-oriented), Metabase (self-hosted) or Looker Studio (Google). Authentication via SSO on Azure AD, Okta or Google Workspace; magic links or MFA for external users. And always an immutable audit log, which is the feature that is worth the most.

Frequently asked questions.

What clients usually want to know before we start.

Can you export all the data from our .accdb file, including the images and attachments?
Yes. Tables, relationships, indexes and records are exported one-to-one via ODBC or an open-source tool. We extract OLE objects and attachments (Access "Attachment" columns) separately and place them in a file store (S3, Azure Blob or GCS), with a reference in the new database. We deliver a mapping document that shows, per table, where each Access column ends up, plus a data quality report listing anomalies that were silently present in Access (empty required fields, broken foreign keys, duplicate primary keys).
What happens to our VBA macros and form events?
We document every macro — what it does, when it is triggered, which data it touches — and discuss with you which ones are still relevant to the new workflow. The relevant macros are rebuilt as backend logic in TypeScript or Python, with tests, so that a later change cannot quietly break a calculation. Macros that have become obsolete over the years or were a workaround for an Access bug are deliberately dropped. At the end you receive a note for every original macro with the decision (kept, revised or dropped — and why).
What if we need to keep working in Access during the migration?
That is the starting point. We set up parallel running: Access remains the operational environment while we build the new web app in staging. In the cut-over phase, a synchronisation layer replicates changes from Access to the new environment every few minutes. Your pilot group is already testing there, while everyone else carries on in Access. At go-live the write direction switches; Access remains available as read-only for reference. A formal rollback procedure is ready and waiting.
What does this cost?
That depends on the size of your .accdb, the number of forms, the complexity of the macros and the target platform. A compact replacement of a smaller administration database with PowerApps or a simple web app is a fixed sprint budget spread over a few sprints. A larger migration with multiple Access files, integrations with your accounting system and a BI layer takes several sprints in succession, delivered in phases per module. We work with a fixed sprint budget so you can adjust the scope each sprint, and we give an indicative figure for the total in the quote — never an empty number before we have seen your Access file ourselves.
How long does a project like this take?
It depends too much on your situation to name a figure here without having seen your .accdb. For a simple replacement we are talking about a track of a few sprints; for a more complex migration with multiple files and integrations, a track of several sprints in a row. We deliver a working partial release every sprint, so you see value early and can adjust priorities. In the quick scan of your file we can give a realistic picture of what is needed for your specific environment.
Can we choose low-code (PowerApps, AppSheet) instead of custom development?
Yes, and in a minority of cases that is the right choice. For relatively generic administrative applications without much custom logic, and for organisations that want to be able to adapt the solution themselves later without a developer, PowerApps with Dataverse or AppSheet with Google Workspace is a sensible route. We then build the PowerApps environment, migrate the data to Dataverse or SQL Server, and set up Power BI for the reporting. The downside: you are tied to that ecosystem. For applications where your own logic lives or the scale goes beyond low-code limits, we choose custom.
How do we handle GDPR, audit trails and healthcare or accountancy compliance?
GDPR compliance is the baseline: encryption in transit (TLS 1.3) and at rest, role-based access with least-privilege principles, data processing agreements where needed, and an immutable audit log of every record change by default. For healthcare environments, we work towards NEN 7510 compliance, with explicit logging of access to and changes in patient records, and session time-outs per office policy. For accountancy and financial services, we meet the Wta requirements on file-keeping and audit. We carry out a DPIA when the scope justifies it, and on request we build penetration tests in as the final sprint before go-live.
Will you work with our current IT provider or support team?
More often than not, yes. We deliver the codebase, build instructions, an architecture overview and an incident runbook so that an external support provider can take over. This is a deliberate design choice to prevent vendor lock-in. During the project, we run a knowledge transfer in the final sprint. Sometimes we continue on a support or further development contract; sometimes an external party is the more logical choice for support. We always advise based on what fits, even if that means another team carries on.
Our Access setup consists of several files that reference one another. Is that a problem?
No. Typically it's a front-end .accdb with linked tables to a back-end .mdb, or several business units that each have their own Access environment with overlapping data. During discovery, we map all the files, identify overlaps and conflicts (the same customer with a different customer number), and propose a common schema. An Access migration is often a good moment to clear up that historically grown mess, as it has to happen during the migration anyway.
What if we only want to modernise the data layer first and keep the Access front-end for now?
That's possible. We set up Postgres or SQL Server as the new back-end and connect your existing Access front-end via ODBC linked tables. Access then becomes a thin presentation layer on top of a modern database; multiple simultaneous users become possible, backups run through professional tooling, and you can start building a web app on the same data in parallel. This is often a good first-step scenario for organisations that don't want to change everything at once. Our page on platform migration describes this phased route in detail.

Talk to us about your Access environment.

A no-obligation introductory call of half an hour. We listen to your current Access workflow and your wishes, ask targeted questions, and give you direction you can use, even if we conclude that a light upgrade is enough rather than a full replacement.

Share LinkedIn Email

Edit content