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.