Route Fits when What catches people out
Keep Access, split and link it Under a handful of users on one office network, and the database mainly needs to stop corrupting. Each user gets a front-end copy; the tables live in one shared back-end file. It's still a file on a share. Wi-Fi and VPN drops mid-write still damage it, and there's still no browser or Mac access.
SQL Server back end, Access front end The data has outgrown the file or the user count, but the forms and reports still work. Microsoft's SQL Server Migration Assistant for Access moves the tables. Queries written for Access can run slowly against SQL Server until they're rewritten, and every user still needs Access installed on Windows.
Power Apps and Dataverse You're on Microsoft 365, want phone and browser access, and the logic is mostly forms and simple rules. Access for Microsoft 365 includes a tool that migrates tables to Dataverse. Dataverse needs paid Power Apps licensing (per user or per app), some field types don't carry over exactly, and the forms and VBA still have to be rebuilt as apps.
Airtable or another no-code database A small team, simple relationships, and you want to edit tables in a browser tomorrow. See our page on Airtable. Record limits per base depend on the plan, and complex queries and VBA logic have no direct equivalent. Custom web app on a real database Several locations, outside users like clients or field staff, or years of business rules hiding in macros that need to work properly. It's the biggest project of the five, so the forms and macros need mapping first. More on that below, and on what custom software costs.