Power Platform

Access to Power Apps Migration: What Actually Takes the Longest

Everyone focuses on the data migration. But in an Access to Power Apps project, the data is rarely what takes the most time. Here is where the hours actually go.

A
Anthony Passeri, MBA
••6 min read
Access to Power Apps Migration: What Actually Takes the Longest

When organizations plan an Access to Power Apps migration, they almost always underestimate the timeline. The reason is consistent: they focus on the data migration and assume everything else will follow quickly.

The data migration is usually the fastest part of the project. Here is where the time actually goes.

Phase 1: Discovery and Documentation (Often Skipped, Always Regretted)

Before a single line of Power Apps code is written, someone needs to understand what the Access database actually does. This sounds obvious, but it is routinely underestimated.

Access databases accumulate business logic over years. Some of it is in queries. Some is in form event procedures. Some is in macros. Some is in the heads of the one person who built the original database and has since moved to a different department.

Discovery involves:

  • Mapping every table and its relationships
  • Documenting every form and what it does
  • Reading every VBA module and understanding the business rules it encodes
  • Interviewing users about their actual workflows (which often differ from what the database was designed to support)

For a medium-sized Access database, this phase takes 2–4 weeks. Skipping it means you will discover requirements mid-build, which is far more expensive than discovering them upfront.

Phase 2: Data Migration to Dataverse (Fast, but Not Instant)

Moving data from Access to Dataverse is largely automated. Microsoft provides tools that handle most of the schema mapping and data transfer. For a well-structured Access database, this can be done in a day or two.

What slows it down:

Data quality issues. Access databases often contain inconsistent data — duplicate records, fields used for multiple purposes, dates stored as text, phone numbers in five different formats. Dataverse has stricter data validation than Access, so data that Access accepted without complaint will fail Dataverse import. Cleaning the data before migration is essential and takes time proportional to how messy the data is.

Schema decisions. Dataverse has different data types and relationship models than Access. Decisions about how to map Access tables to Dataverse entities — especially many-to-many relationships and lookup fields — require thought and sometimes iteration.

Calculated fields and rollups. Business logic that lived in Access queries needs to be recreated as Dataverse calculated columns or rollup fields. This is not difficult, but it takes time.

Phase 3: Power Apps Front-End Build (The Bulk of the Work)

This is where most of the project time goes. Rebuilding an Access front end in Power Apps is not a translation — it is a rebuild. Power Apps has a different programming model, different controls, and different limitations than Access.

Canvas apps vs. model-driven apps. The first decision is which type of Power App to build. Canvas apps give you full control over the layout and are better for custom workflows. Model-driven apps are faster to build but follow Dataverse's structure closely. Most Access migrations end up with a mix of both, which adds complexity.

Form complexity. A simple Access form with a few fields maps to Power Apps straightforwardly. A complex form with subforms, conditional formatting, calculated fields, and VBA event procedures takes significantly longer. Each piece of VBA logic needs to be reimplemented in Power Fx, Power Apps' formula language.

Navigation and user experience. Access applications often have elaborate navigation forms, switchboards, and custom menus. Recreating this navigation in Power Apps requires deliberate design work.

Reports. Power Apps does not have a native reporting engine comparable to Access Reports. Reports typically need to be rebuilt in Power BI, which is a separate tool with its own learning curve. If your Access database has 20 reports, plan for each one to take meaningful time in Power BI.

Phase 4: Business Logic Migration (Underestimated Every Time)

VBA is the most time-consuming part of any Access migration. Not because it is technically difficult to port, but because it requires understanding what the code is supposed to do before you can rewrite it.

Common VBA patterns in Access and their Power Apps equivalents:

  • Form validation → Power Fx formulas and Power Apps form validation
  • Calculated fields → Power Fx expressions or Dataverse calculated columns
  • Email sending → Power Automate flows
  • File operations → SharePoint integration or Azure Blob Storage
  • Excel automation → Power Automate with Excel connector
  • Custom dialogs → Power Apps popup screens or overlays

Each of these translations is straightforward once you know what the VBA is doing. The time is in the understanding, not the writing.

Phase 5: Testing and User Acceptance (Always Takes Longer Than Planned)

Users who have worked with an Access database for years have developed precise mental models of how it behaves. Power Apps will behave differently in subtle ways — different keyboard shortcuts, different tab order, different error messages — and users will notice every difference.

Plan for at least two rounds of user acceptance testing. The first round will surface functional gaps. The second round will surface usability issues. Both are important.

Realistic Timeline Expectations

For a medium-sized Access database (10–30 tables, 10–20 forms, moderate VBA):

PhaseTypical Duration
Discovery and documentation2–4 weeks
Data migration to Dataverse1–2 weeks
Power Apps front-end build6–12 weeks
Business logic migration2–4 weeks
Testing and UAT2–4 weeks
Total13–26 weeks

These ranges are wide because complexity varies enormously. A database with clean data, simple forms, and minimal VBA can move faster. A database with years of accumulated complexity will take longer.

What You Can Do to Speed Things Up

Document before you start. Every hour spent documenting requirements before the build saves two hours of rework during it.

Prioritize ruthlessly. Identify the core workflows that 80% of users use 80% of the time. Build those first and get them into production. Everything else can follow in a second phase.

Involve users early. Get users into the Power Apps prototype as early as possible. Feedback in week 3 is far cheaper than feedback in week 12.

Do not try to replicate Access exactly. Power Apps is a different tool. Some things that were awkward in Access are elegant in Power Apps, and vice versa. Be open to redesigning workflows rather than just translating them.

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.

Want a realistic timeline for your specific Access to Power Apps migration? Schedule a free assessment and find out what will take the most time.

Schedule a Free Call →

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.

A

Written by

Anthony Passeri, MBA

Access Expert and Editor

Bridging the gap between Access and the Future

Explore Topics

#Power Apps#migration#timeline#planning#Power Platform

Keep reading

More on Power Platform