Short answer: Inventory everything in the database first, pick a destination that fits the problem you’re solving (usually Power Apps with Dataverse, or SQL Server behind your existing Access screens), clean the data before you move it, and run old and new side by side before switching over. A simple database takes 40 to 80 hours; a complex one can take months.
Converting a legacy Access database is one of the most consequential technology decisions a small or mid-sized organization makes. Done well, it clears years of technical debt and opens the door to mobile access, real-time collaboration and modern integrations. Done poorly, it disrupts operations and loses the knowledge built into the original system. This guide walks through the full process.
Step 1: Decide Whether You Need to Migrate at All
Not every old Access database needs replacing. Migrate when there’s real pain: crashes or data loss, users who need mobile or remote access, a move to the cloud, a database near the 2 GB limit, or security and audit requirements Access can’t meet.
If none of that applies, a well-maintained, split Access database may serve you for years, especially with ongoing maintenance and support. Migration for its own sake is expensive and risky; migration to solve a real problem is an investment. For the full checklist, see How to Know When It’s Time to Migrate Off Microsoft Access.
Step 2: Inventory What You Actually Have
The single biggest mistake in Access migrations is underestimating the existing system. Before choosing a platform, take stock of:
- Tables and data volume. How many tables and records? Are relationships enforced in the database, or only by the application?
- Queries. Pay special attention to action queries (update, delete, append, make-table). They hold business logic that must be rebuilt.
- Forms and workflows. Subforms, conditional formatting, calculated controls and cascading dropdowns are all logic to rebuild, not just copy.
- Reports. Who runs each one, and how often? Don’t rebuild reports nobody has opened in years.
- VBA code. This is where old databases hide most of their complexity. Open every module and every form’s code, and write down what it does in plain language. Automation, validation, API calls, and links to Outlook, Excel or Word all need a plan.
- Macros. Older databases may use legacy macros that need to be understood and translated.
- External connections. Linked tables, Excel or CSV imports and exports, and email sent through Outlook each need handling.
If nobody can explain how the system works, start with legacy system documentation. It’s the foundation of an accurate quote and a smooth migration.
Step 3: Choose the Right Destination Platform
There’s no single right answer. The best fit depends on your infrastructure, how complex the application is, and your budget.
| Platform | Best for | Licensing | Effort |
|---|---|---|---|
| Power Apps + Dataverse | Most business apps that need mobile, cloud or many users | Power Apps Premium per user | Full rebuild of screens |
| Access front end + SQL Server back end | Access screens work fine; the data layer is the problem | SQL Server (Express is free for smaller databases) | Lowest disruption |
| Power Apps + SharePoint lists | Simple apps with a few tables and modest record counts | Usually included in Microsoft 365 | Moderate |
| Azure SQL + custom web app | Public-facing apps, large user bases, complex logic | Varies | Full custom development |
Power Apps + Dataverse
This is the natural modern successor to Access for most business applications. Dataverse is a true relational database with role-based security, audit logging and compliance features built in. Power Apps provides the screens, and Power Automate replaces VBA automation and workflows. It integrates natively with Teams, SharePoint and Outlook.
It isn’t free: each user generally needs a Power Apps Premium license. It’s the right choice for internal apps that need to go mobile, go cloud, or support more users than Access can. Learn more in The Case for Power Apps and our Access to Power Platform migration service.
Access Front End + SQL Server Back End
This is the lowest-disruption path when your Access forms and reports still serve users well but the data layer is struggling. You move the tables to SQL Server, relink them in Access through ODBC, and the front end keeps working largely unchanged. It removes the 2 GB limit, handles many more simultaneous users, and gives you enterprise-grade data security without a rebuild. See our Access to SQL Server migration service.
Power Apps + SharePoint Lists
This works well for simple data models. SharePoint lists have limits, including a 5,000-item list view threshold and weak support for complex relationships. But for a few tables with modest record counts, it’s affordable and easy to reach from anywhere.
Azure SQL + Custom Web App
Choose this when the application must be public-facing, has very complex logic or serves a large user base. It’s a full redevelopment project, with the cost and timeline of custom software. Reserve it for apps that truly need it.
Other Low-Code Platforms
Airtable, Zoho Creator, AppSheet and similar tools can work for simple cases, but they add a vendor outside the Microsoft ecosystem, which creates long-term integration friction for organizations already on Microsoft 365. For a deeper comparison, see What Is the Best Replacement for Microsoft Access?
Step 4: Design the New Data Model First
Migrating an Access database isn’t the same as copying it. Old databases often have redundant fields, unnormalized tables, stored values that should be calculated, and relationships that exist only informally. The migration is your chance to fix these, not carry them forward.
Review each table for normalization. Make sure every table has a meaningful primary key. Map relationships explicitly. Find lookup values that are hard-coded in VBA and move them into tables. Clean up field names: Access tolerates spaces in names, and they cause pain on modern platforms.
If the data model is sound, recreating it is straightforward. If it grew organically over 15 years, the migration is also a redesign. Budget accordingly.
Step 5: Migrate and Clean the Data
A typical data migration follows this sequence:
- Export or connect to the Access tables.
- Inspect for duplicates, blanks in required fields, broken references, inconsistent formatting, and free-typed values that belong in lookup tables.
- Clean the data before loading it, not after.
- Load it with the right tool for the destination.
- Check record counts and spot-check values against the original.
- Confirm calculated values match.
Microsoft provides free tools for the load step. Access’s built-in Export to Dataverse wizard creates tables in Dataverse and moves the data, and SQL Server Migration Assistant (SSMA) for Access converts tables to SQL Server and can relink them in Access. Larger or messier datasets may need Power Automate flows or scripts.
Data problems that were invisible in Access, because the application worked around them, become obvious on a platform with stricter rules. This is almost always more work than expected.
Step 6: Rebuild the Application Layer
For complex databases, this is the largest part of the project. Every form, workflow and report needs a counterpart.
In Power Apps, canvas apps give you the most layout control and feel most like Access forms. Model-driven apps offer less design freedom but come with Dataverse’s built-in views, forms and business rules, which is faster for straightforward data entry. Power Automate replaces VBA for triggers, email notifications, approvals and scheduled tasks; our VBA vs Power Automate whitepaper maps one to the other. Power BI replaces Access reports for analysis.
Rebuild in order of user impact: daily screens first, rarely used reports last. Involve real users throughout, not just at the end. The knowledge of how the old system works lives in the people who use it, not in documentation that probably doesn’t exist.
Step 7: Run Both Systems in Parallel
Never switch over cold. Run the old Access database and the new application side by side for a set period, typically two to four weeks for a moderately complex system. This surfaces missing features, data mismatches and logic that wasn’t rebuilt correctly, and it gives users time to trust the new system.
Set a firm cutover date in advance and stick to it. Parallel periods with no end date drag on, double everyone’s workload and undermine adoption.
Step 8: Train Users and Document the New System
People who have used an Access database for years have deep muscle memory. The new platform will handle navigation, search, data entry and reports differently. Training isn’t optional, and it shouldn’t be a single one-hour session the day before launch.
Document the new system in plain language: how to add records, find information, export data, and who to call when something breaks. Screenshots help; short videos help more. A guide on SharePoint that’s actually kept up to date beats a training deck nobody can find six months later.
Planning a migration? Book a free diagnostic and we’ll review your database and give you a realistic scope.
What an Access Migration Really Costs
Access migrations are routinely underestimated. Here’s a realistic framework for migrating to Power Apps on Dataverse, including data migration and testing:
| Database complexity | Typical profile | Estimated effort |
|---|---|---|
| Simple | 5 to 10 tables, basic forms, little VBA, clean data | 40 to 80 hours |
| Moderate | 15 to 30 tables, significant VBA, custom reports, some integrations | 150 to 300 hours |
| Complex | 30+ tables, heavy VBA business logic, many connections, years of messy data | 500+ hours, over several months |
These ranges assume an experienced developer who knows the destination platform. Teams learning the platform while they migrate should expect much longer timelines. See examples of real projects in our case studies.
The Payoff
A well-executed migration delivers what the old system can’t: access from any device, real security with individual accountability, automated workflows that don’t depend on someone remembering, a data layer without file size walls, and integration with the rest of Microsoft 365.
More than that, it delivers confidence: in the data, in the process, and in your ability to build on the system instead of just keeping it alive. That confidence is what the project is really for.
Frequently Asked Questions
How long does it take to migrate an Access database?
A simple database takes about 40 to 80 hours of development. A moderately complex one takes 150 to 300 hours. Complex systems with heavy VBA can run 500+ hours over several months.
What is the best platform to migrate Access to?
For most business apps, Power Apps with Dataverse. If your Access screens work well and only the data is struggling, move the tables to SQL Server and keep Access as the front end. Simple apps can use SharePoint lists.
Can I keep using Access after migrating?
Yes. With a SQL Server or Dataverse back end, your team can keep using the Access forms and reports they know while the data lives in a sturdier database.
Is there a free tool to migrate Access to SQL Server?
Yes. Microsoft’s SQL Server Migration Assistant (SSMA) for Access is free. It converts tables and data and can relink them in Access. Queries, forms and VBA still need review and testing.
Anthony Passeri, MBA, is the founder of Access Evolved and a certified Microsoft Access Expert with 21+ years of Access and relational database experience. He helps businesses keep critical Access databases running and modernize them to Power Platform or SQL Server. More about Anthony
Talk to an Access Expert
Not sure what this means for your database? Book a free diagnostic call. No sales pitch, just a straight conversation about what makes sense for your situation.
Phone: 623-267-5720
Email: info@accessevolved.com
Access Evolved | 19580 W Indian School Rd, Ste 105 #815, Buckeye, AZ 85396
