The Complete Guide to Microsoft Access Database Migration & Modernization (2027)
A complete framework for Microsoft Access migration in 2027 — covering every migration path, the seven-stage modernization process, common mistakes, and how to choose the right architecture for your specific database.
Microsoft Access has powered business applications for decades.
Across companies large and small, Access databases still manage customers, inventory, orders, projects, billing, compliance, scheduling, reporting, manufacturing processes, and countless other critical business functions.
Many of these applications started simply.
Someone created a few tables. Then came queries. Forms were added. Reports followed. VBA automated repetitive tasks. Excel exports appeared. Perhaps SQL Server or an accounting system was eventually connected.
Ten or twenty years later, that "little Access database" may have become an application the organization cannot operate without.
That's when modernization becomes complicated.
Migrating Microsoft Access isn't simply a matter of copying tables into another database. A mature Access application can contain years of business logic embedded throughout forms, queries, macros, reports, VBA modules, relationships, and integrations.
The challenge is preserving that business knowledge while replacing the parts of the application that have become difficult to maintain, scale, secure, or deploy.
This guide explains how I approach Microsoft Access migration and modernization in 2027, including the major migration paths available today and the decisions organizations should make before replacing an existing Access application.
What Does Microsoft Access Modernization Mean?
Modernization does not necessarily mean eliminating Microsoft Access.
That's one of the most important distinctions to understand.
There are several legitimate modernization strategies:
Access → SQL Server Keep the Access front end while moving the data to SQL Server.
Access → Azure SQL Similar architecture, but with the database hosted in Microsoft's Azure cloud.
Access → Dataverse Move the data into Microsoft's Dataverse platform while potentially continuing to use Access during a transition period.
Access → Power Apps + Dataverse Rebuild the application's user interface using Power Apps while storing the data in Dataverse.
Access → Power Apps + SharePoint For appropriate applications, SharePoint Lists can provide a simpler Microsoft 365-based data layer.
Access → Custom Web Application Rebuild the application using technologies such as .NET, JavaScript frameworks, SQL Server, Azure, or another application stack.
Hybrid modernization Keep selected Access functionality while modernizing the database, workflows, reporting, integrations, or user interfaces.
Microsoft itself supports hybrid scenarios. For example, Microsoft documents the ability to migrate Access data to Dataverse while continuing to use the existing Access desktop application through linked tables. The same underlying data can then be used by Power Apps and other Power Platform services.
The correct strategy depends on the application.
Why Organizations Modernize Microsoft Access
Most organizations don't wake up one morning and decide that they dislike Access.
There is usually a business problem driving the project.
Common reasons include:
Remote access — An Access application designed for employees on a local network may become difficult to use when employees work remotely or from multiple offices.
Mobile access — Users may need to enter or retrieve information from phones or tablets.
Scalability — The application may have outgrown the practical limits of its original architecture. Microsoft currently documents an Access database size limit of 2 GB. Microsoft recommends SQL Server as one potential migration path when an Access database needs greater database capacity or concurrency.
Reliability — An application may have become increasingly difficult to maintain as more users, tables, integrations, and business rules have been added.
Security — Organizations may require centralized authentication, role-based security, auditing, or more sophisticated data governance.
Integration — The Access application may need to communicate with Microsoft 365, Dynamics 365, QuickBooks, Salesforce, ERP systems, APIs, SharePoint, SQL Server, Azure services, Power BI, and other business applications.
Automation — Processes performed manually in Access may be candidates for Power Automate or other workflow technologies.
Knowledge risk — Sometimes the biggest problem isn't Access at all. It's the fact that the employee or developer who understands the database is retiring. An application containing 15 years of undocumented VBA can represent a substantial operational risk.
Don't Start by Rebuilding the Application
This is one of the most common mistakes I see in Access migration projects.
A company decides: "We need to convert this Access database to Power Apps."
Developers immediately begin rebuilding screens.
That's backwards.
Before choosing the replacement technology, you need to understand what the Access application actually does.
A proper migration begins with discovery.
Step 1: Inventory the Existing Access Application
Before changing anything, document it.
At minimum, inventory:
- Tables, fields, primary keys, relationships, and indexes
- Queries, forms, subforms, reports, and macros
- VBA modules
- Linked tables and ODBC connections
- Excel imports and exports
- Email automation
- File system dependencies
- Scheduled processes
- External databases and APIs
- User permissions and startup logic
You also need to understand how people actually use the application.
That isn't always obvious from examining the database.
A form might exist but hasn't been used in eight years. Another form may look insignificant but might be the screen a department uses 200 times every day.
Technical inventory and operational inventory are therefore two different things. You need both.
Step 2: Identify the Business Processes
Next, stop thinking about Access objects. Think about workflows.
Suppose an application contains 37 tables, 112 queries, 28 forms, 14 reports, and 9 VBA modules.
That tells me something about the technical complexity. But it doesn't tell me what the system does.
Instead, map processes such as:
Customer created → order entered → manager approves → invoice generated → customer notified → payment recorded
That's what needs to survive the migration.
Forms and queries are implementations. Business processes are the application.
Once those processes are understood, you can decide how they should work in the modern system.
Step 3: Find the Hidden Business Logic
This is where Access migrations often become much more complicated than expected.
Business rules may be scattered throughout VBA, query expressions, form events, control sources, validation rules, macros, default values, report events, calculated controls, and SQL strings generated by VBA.
For example, a button labeled Create Invoice might execute VBA that:
- Validates the customer
- Checks outstanding balances
- Calculates pricing
- Creates invoice records
- Updates inventory
- Generates a PDF
- Saves the PDF
- Emails the customer
- Updates an audit table
Recreating the button visually is easy. Discovering everything behind the button is the real migration work.
Step 4: Clean the Data Before Migrating It
Migration exposes years of accumulated data problems.
Typical examples include duplicate customers, missing primary keys, inconsistent addresses, invalid dates, orphan records, duplicate IDs, inconsistent naming conventions, text stored where numbers should be used, numbers stored as text, obsolete records, unused columns, and missing relationships.
Moving bad data into Dataverse or SQL Server doesn't fix it. It simply creates a modern database containing old problems.
A migration project is an excellent opportunity to establish proper primary keys, foreign keys, referential integrity, data types, naming standards, validation rules, and duplicate handling.
Microsoft specifically recommends reviewing indexes, primary keys, relationships, and compatible field types before migrating Access data to SQL Server.
Choosing the Right Microsoft Access Migration Path
There is no universal replacement for Access. Here are the major options.
Option 1: Keep Access and Move the Data to SQL Server
This is one of the most practical modernization strategies for many mature applications.
Instead of replacing everything, you separate the application into two layers.
Front end: Microsoft Access continues providing forms, reports, VBA, queries, and the user interface.
Back end: SQL Server stores the data. Access communicates with SQL Server using linked tables and ODBC.
This can preserve a substantial amount of an organization's existing investment.
Microsoft provides SQL Server Migration Assistant (SSMA) specifically to assist with Access-to-SQL Server migrations. SSMA can migrate database structures such as tables, columns, keys, indexes, and certain queries. Microsoft notes, however, that Access forms, reports, macros, and VBA modules are not automatically converted by SSMA.
That's an extremely important point. There is no magic "convert my Access application" button.
When Access + SQL Server makes sense:
- Users primarily work on Windows PCs
- Existing Access forms work well
- Existing reports are valuable
- Significant VBA logic already exists
- The main problem is the database back end
- You need more robust centralized data
- A complete rewrite would provide little immediate business value
Option 2: Access to Azure SQL
Azure SQL provides another path when organizations want SQL Server capabilities without maintaining an on-premises SQL Server installation.
The architecture can still be: Access front end → Azure SQL database.
This can work particularly well when organizations already use Azure infrastructure. However, cloud database architecture introduces considerations such as network latency, query efficiency, authentication, security, firewall configuration, and connection reliability.
A poorly designed Access application that retrieves enormous datasets across a local network may perform even worse when that database is moved hundreds of miles away. Cloud migration therefore requires query optimization.
Option 3: Access to Dataverse
Dataverse is Microsoft's cloud data platform underlying much of Power Platform and Dynamics 365.
Microsoft provides tools for migrating Access data into Dataverse. After migration, organizations can potentially use the same data from Access, Power Apps, Power Automate, Power BI, Dynamics 365, and other Power Platform components.
Microsoft also supports scenarios where the existing Access application continues working against migrated Dataverse tables. That creates an interesting migration strategy — you don't necessarily need to replace Access immediately. You can modernize incrementally.
A phased Access-to-Dataverse migration:
- Phase 1: Access front end + Access back end
- Phase 2: Access front end + Dataverse
- Phase 3: Access + Power Apps + Dataverse
- Phase 4: Power Apps + Dataverse
This reduces the risk associated with replacing everything simultaneously and allows departments to transition gradually.
Dataverse data-type considerations: Access and Dataverse are not identical databases. Microsoft's migration tooling supports many common Access types, including Short Text, Long Text, AutoNumber, Date/Time, Currency, Decimal, Yes/No, integers, lookups, hyperlinks, and attachments — subject to specific migration rules and limitations.
Some Access constructs require special treatment. For example, Microsoft currently identifies OLE Object and Rich Text as unsupported for direct Access-to-Dataverse migration, while calculated fields require different handling because calculations need to be recreated appropriately in Dataverse.
This is exactly why migration assessment should occur before development begins.
Option 4: Access to Power Apps + Dataverse
This is often what organizations mean when they say: "We want to replace Access."
Power Apps becomes the user interface. Dataverse becomes the database. Power Automate can provide workflow automation. Power BI can provide analytics and dashboards.
Microsoft describes Dataverse as a secure cloud-based business data platform that Power Apps can connect to directly for displaying, creating, and updating records.
Canvas Apps vs. Model-Driven Apps
If Power Apps is selected, another architectural decision appears.
Canvas apps provide substantial control over screen layout and user experience. They're often appropriate when you're replacing a highly customized Access form-based application.
Model-driven apps are driven primarily by the underlying Dataverse data model. They can be excellent for structured business applications where standardized forms, views, relationships, and business processes are more important than highly customized screen layouts.
Sometimes the correct answer is a combination. Don't automatically choose canvas apps simply because Access had forms. Choose the application model based on the workflow.
Option 5: Access to Power Apps + SharePoint
Not every application requires Dataverse. SharePoint Lists can sometimes provide a cost-effective data source for simpler Power Apps solutions.
Good candidates generally have relatively simple relationships, moderate data volumes, straightforward security, simple workflows, and limited transactional complexity.
But SharePoint should not automatically be chosen simply because it's available. A complex relational Access application can become difficult to reproduce cleanly with SharePoint Lists. Dataverse or SQL Server may be the better architectural choice.
Option 6: Rebuild as a Custom Web Application
Sometimes Power Platform isn't the correct destination.
A custom application may be appropriate when you need public-facing access, highly customized interfaces, complex integrations, specialized performance requirements, very large workloads, custom authentication, precise control over architecture, or a product intended for external customers.
Technologies might include .NET, SQL Server, Azure, React, Angular, Node.js, PostgreSQL, AWS, and other modern application frameworks.
The migration methodology remains similar: understand the existing application before replacing it.
What Happens to Access Forms?
Access forms generally don't automatically become Power Apps screens. They need to be redesigned.
That's not necessarily bad. A 15-year-old Access form may contain 50 fields, 17 buttons, six tabs, and four subforms. Recreating it pixel-for-pixel may simply reproduce an outdated interface.
Instead ask: What is the user trying to accomplish on this screen? Then design the new experience around that task.
What Happens to Access Queries?
Queries require careful analysis. Some can become Dataverse views, Power Fx formulas, SQL views, stored procedures, Power Automate logic, or Power BI transformations. Others should remain database queries.
Complex Access queries may contain Access-specific functions or syntax that don't translate directly to SQL Server. Microsoft specifically notes that SSMA does not convert every Access query and that Access-specific functions or syntax may require manual conversion to T-SQL.
What Happens to VBA?
VBA is frequently the largest unknown in an Access migration. There is no one-to-one replacement.
VBA functionality may become Power Fx, Power Automate flows, Dataverse business rules, plugins, SQL procedures, Azure Functions, JavaScript, application logic, or APIs.
The correct destination depends on what the VBA actually does. This is why counting lines of VBA isn't enough. You need to classify the functionality.
What Happens to Access Reports?
Access has an extremely capable reporting engine. Organizations often underestimate how much work is involved in replacing mature reports.
Potential replacements include Power BI, Power BI paginated reports, Power Apps, Word templates, Excel, SSRS, PDF generation, and custom reporting solutions.
Sometimes keeping Access solely for reporting during a transition is perfectly reasonable. Modernization doesn't need to be ideological. It needs to solve the business problem.
Don't Forget Integrations
An old Access database may quietly communicate with half the company.
Look for Excel files, CSV files, Outlook, Word, SQL Server, ODBC databases, QuickBooks, FTP servers, shared network folders, APIs, websites, barcode systems, scanners, scheduled Windows tasks, and more.
These dependencies need to be identified before the old application is retired.
Security Should Be Redesigned, Not Copied
Modernization provides an opportunity to rethink security.
Instead of asking "How do we reproduce the old Access password system?" ask "Who should have access to what information?"
A modern solution may incorporate Microsoft Entra ID, Dataverse security roles, Teams, Microsoft 365 groups, environment security, row-level permissions, and auditing.
Security requirements should be part of architecture — not something added after development.
Performance Matters
A Power Apps application that technically works isn't necessarily a good replacement.
Performance should be designed from the beginning. Consider data volume, query patterns, delegation, number of network requests, relationships, indexing, app initialization, images and attachments, API calls, and automation frequency.
Microsoft recommends testing Power Apps on the actual device types and network conditions expected in production because performance can vary based on device capability, connectivity, application complexity, and other factors.
Test with realistic data. An application containing 100 sample records tells you almost nothing about how it will behave with 500,000 production records.
The Access Evolved Migration Framework
Over years of working with Microsoft Access and business data systems, I've found that successful modernization projects generally follow seven stages.
1. Discover Understand the application, users, workflows, pain points, dependencies, and business objectives.
2. Document Inventory tables, relationships, queries, forms, reports, VBA, macros, integrations, and security.
3. Stabilize Correct critical data problems, identify obsolete components, establish backups, and reduce unnecessary complexity.
4. Architect Select the appropriate destination: Access + SQL Server, Access + Azure SQL, Access + Dataverse, Power Apps + Dataverse, Power Apps + SharePoint, custom application, or hybrid architecture.
5. Migrate Move the data and rebuild the required application functionality.
6. Validate Compare the new system against the old system. Validate record counts, calculations, workflows, reports, permissions, integrations, and performance.
7. Deploy Move users into production with training, documentation, support, rollback planning, and post-launch monitoring.
Discover → Document → Stabilize → Architect → Migrate → Validate → Deploy
The technology changes. This process remains remarkably consistent.
Why Parallel Testing Matters
Never assume that because the new application opens successfully, the migration succeeded.
Run real business scenarios through both systems. Create the same customer. Enter the same transaction. Run the same calculation. Generate the same report. Compare the results.
Have actual users test the system. Developers know how the application was designed. Users know how the business actually operates. You need both perspectives.
Data Validation After Migration
At minimum compare total record counts, records by major category, financial totals, date ranges, null values, parent/child relationships, duplicate records, and key calculations.
For important systems, automate reconciliation wherever possible. "Everything looks right" isn't a data validation strategy.
The Big-Bang Migration vs. Phased Migration
Big Bang: Old system stops. New system starts. This may be appropriate for smaller applications.
Phased Migration: Components move gradually. For example:
- Phase 1: Move Access tables to SQL Server
- Phase 2: Replace manual processes with Power Automate
- Phase 3: Build Power Apps for remote employees
- Phase 4: Replace remaining Access forms
- Phase 5: Move reporting to Power BI
This often reduces risk substantially.
How Long Does an Access Migration Take?
There is no meaningful answer based solely on database file size.
A 1.5 GB Access database with ten simple forms may be easier to migrate than a 100 MB database containing hundreds of queries and 30,000 lines of VBA.
Complexity is driven by the number of tables, relationships, data quality, queries, forms, reports, VBA, macros, integrations, security requirements, number of workflows, number of users, and testing requirements.
The best way to estimate a migration is to assess the existing application first.
How Much Does Microsoft Access Migration Cost?
A straightforward SQL Server back-end migration may be relatively small. A complete rebuild involving Power Apps, Dataverse, dozens of screens, workflows, APIs, dashboards, role-based security, and historical data conversion is an application development project.
The fact that the old system happens to be Access doesn't make the replacement simple.
A proper assessment should produce a current-state inventory, recommended architecture, migration scope, risks, assumptions, estimated effort, and implementation phases. Only then can the project be priced responsibly.
Should You Replace Microsoft Access?
Not necessarily.
If an Access application works reliably, has a manageable number of users, meets security requirements, performs well, is actively maintained, and doesn't require web or mobile access — there may be little reason to replace it.
Microsoft Access remains included in current Microsoft 365 offerings, and Microsoft's current documentation continues to support Access 2024 and Access for Microsoft 365. Microsoft's own documentation also describes modernization paths that preserve Access as a front end while moving data to SQL Server or Dataverse.
Sometimes the best modernization decision is: Keep Access. Modernize what's underneath it.
When Should You Seriously Consider Migration?
Migration deserves consideration when:
- The application is business-critical but poorly understood
- Remote users can't access it effectively
- Mobile access is required
- The database is approaching technical limitations
- Multiple offices need simultaneous access
- Security requirements have changed
- The original developer is leaving
- The application depends heavily on obsolete components
- Integration requirements have grown
- Users spend significant time performing manual workarounds
- Maintenance costs are increasing
- The application has become a barrier to business growth
The presence of Access itself isn't the problem. The question is whether the current architecture still serves the organization.
Common Microsoft Access Migration Mistakes
After working with Access systems for many years, several mistakes appear repeatedly.
Mistake 1: Choosing the destination before assessing the application "Everything must go into Power Apps" isn't an architecture strategy.
Mistake 2: Treating migration as data conversion Tables may be only a fraction of the application.
Mistake 3: Ignoring VBA VBA often contains critical business logic.
Mistake 4: Rebuilding every old feature Some functionality exists only because of limitations that no longer apply.
Mistake 5: Ignoring data quality Bad data doesn't improve because it moved to the cloud.
Mistake 6: Recreating the old interface exactly Modernization is an opportunity to improve workflows.
Mistake 7: Underestimating reports Complex Access reporting can require substantial replacement work.
Mistake 8: Migrating everything at once Phased modernization can significantly reduce risk.
Mistake 9: Testing with unrealistic data Production-scale testing matters.
Mistake 10: Turning off Access too soon Keep the legacy application available until the replacement has been validated and accepted.
Microsoft Access Migration Checklist
Before beginning an Access modernization project, answer these questions.
Application
- How many Access databases are involved?
- Are they ACCDB or MDB?
- Are they split front-end/back-end applications?
- How many users are there?
- Where are the files located?
Data
- How many tables? How much data?
- Are primary keys present? Are relationships enforced?
- Are duplicates present?
- Are attachments or OLE objects used?
Interface
- How many forms? Which forms are actually used?
- Are subforms heavily used?
- Which workflows are business-critical?
Logic
- How many queries? How much VBA exists?
- Are macros used? Where are calculations performed?
Reporting
- Which reports are still required?
- Which reports are regulatory or financial?
- Could some reports become Power BI dashboards?
Integration
- Does Access communicate with Excel, Outlook, SQL Server, accounting systems, APIs, shared folders, or other databases?
Security
- Who can access the application?
- Are different permission levels required?
- Is auditing required? Is sensitive information stored?
Future Requirements
- Mobile? Browser? Remote access? Automation? Dashboards? External users? API integration?
Only after answering these questions should you select the target architecture.
Final Thoughts
Microsoft Access modernization isn't about declaring Access "old" and replacing it with something newer.
It's about protecting the business knowledge that has accumulated inside an application — sometimes over decades — while creating an architecture capable of supporting the organization's future.
The safest migration isn't necessarily the one that replaces the most technology. It's the one that understands the existing system, preserves what matters, eliminates what doesn't, and introduces new technology where it creates genuine business value.
For one organization, that might mean Access with SQL Server. For another, it might mean Dataverse. Another may need Power Apps, Power Automate, and Power BI. And another may require a completely custom web application.
The first question therefore shouldn't be: "What should replace Microsoft Access?"
It should be: "What does this Access application do for the business, and what is the best architecture for doing that job over the next decade?"
Answer that correctly, and the technology decision becomes much easier.
Work With Access Evolved
If you found this article useful, Access Evolved specializes in exactly this kind of work — from hands-on Microsoft Access support to full database modernization projects.
Ready to assess your Access database and build a migration roadmap? Schedule a free call with Anthony Passeri.
Thinking about migrating?
Ready to move beyond Microsoft Access?
Access is a great starting point, but growing businesses often hit its limits. Anthony Passeri specializes in migrating Access databases to modern platforms — Power Platform, Power Apps, SQL Server, Azure, and more — so you keep your data and workflows without the headaches.
Written by
Anthony Passeri, MBA
Access Expert and Editor
Bridging the gap between Access and the Future
Explore Topics
Keep reading
More on Migration
Is Microsoft Access Being Replaced? What the October 2026 End-of-Support Date Actually Means
Microsoft Access reaches end of mainstream support in October 2026. Here is what that actually means for your database, what it does not mean, and the honest options in front of you right now.
Microsoft Dataverse: The Database Behind Power Platform
Dataverse is the cloud database that powers Power Apps and Power Automate. Learn what it is, how it compares to Access, and when to consider migrating.
Migrating from Access to Power Apps: A Complete Roadmap
The technology is not the hard part. Here is what a real Access to Power Apps migration actually involves — including the parts that take longer than anyone expects.