MS Access Blog — Free Resource

Access Migration Readiness Checklist

47 questions to answer before you start — by Anthony Passeri, MBA

How to use this checklist: Work through every section before you scope a migration project or choose a destination platform. Items phrased as statements are checkboxes. Items phrased as questions require a written answer. The goal is to surface unknowns before they become expensive surprises in Phase 3 or 4.

1. Database Inventory

Count every table and note current record volumes

Count VBA lines across all modules — read them, don't just count

Classify every query: SELECT, aggregate, action, or complex multi-table

List every form and note which ones users interact with daily

List every report and assess whether Power BI can replace it

Document every macro and its trigger

Identify any fields storing files, images, or OLE objects

Note any calculated fields or complex default values

Map every table relationship and referential integrity rule

Identify tables with more than 100,000 records

2. Integration Mapping

List every system that imports data into Access

List every system that receives exports from Access

Document every Excel export and who uses it

Identify any Outlook or email automation in VBA

Note any file system operations (reading/writing files)

Document any external database connections

Identify any scheduled tasks or Windows Task Scheduler jobs

Note any SharePoint or network share dependencies

Document any third-party add-ins or references

3. Risk Assessment

Has the database experienced corruption in the last 2 years?

Is there a current backup strategy? When was it last tested?

How many people can have the database open simultaneously?

Is there a single person who maintains the database? What is their tenure?

Does the database handle regulated data (HIPAA, SOX, GDPR, PCI)?

Are there audit trail requirements that Access currently does not meet?

What is the cost of one hour of downtime for the affected team?

What is the cost of losing one week of transaction data?

Are there any compliance deadlines that affect the migration timeline?

What is the current Access version and is it still supported?

4. Platform Selection

Do users need mobile or browser-based access?

Are all users on Windows desktops, or are there Mac or remote users?

What Microsoft 365 licenses does the organization currently hold?

Is Power Apps per-app or per-user licensing already in the budget?

Is SQL Server already in the environment?

What is the organization's cloud readiness and Azure footprint?

Who will maintain the new system after migration?

Does the IT team have Power Platform experience, or will training be needed?

Are there complex reports that require pixel-perfect layout (invoices, compliance)?

Is offline access to a local file genuinely required?

5. Timeline & Cost Planning

Has a formal discovery phase been scoped and budgeted?

Is the timeline built from the phases, or was it set before discovery?

Has the VBA complexity been factored into the build estimate?

Is there budget for parallel running (both systems simultaneously)?

Has user training time and productivity dip been budgeted?

Is there a rollback plan if a critical problem is found post-go-live?

Has internal time (requirements, testing, training) been costed?

Is there executive sponsorship and a named project owner?

Have the users who will do UAT been identified and committed?

Is there a realistic cutover date that accounts for all phases?

6. Business Case

Has the annual cost of staying on Access been calculated?

Have manual workaround hours been documented and costed?

Has the key person dependency risk been quantified?

Has the compliance exposure been assessed with legal or compliance?

Has the 3-year total cost of migration (including licensing) been calculated?

Has the payback period been calculated?

Has the 'why now' question been answered for the CFO?

Has a phased approach been considered to reduce the initial investment?

7. Go / No-Go Decision

Is the business case approved?

Is the destination platform confirmed?

Is the discovery phase scoped and resourced?

Is there a named project owner with authority to make decisions?

Are the key users committed to participating in requirements and UAT?

Is there a realistic timeline that was built after discovery, not before?

Is there a rollback plan?

Is the migration being treated as a business process redesign, not just a technology swap?

What to do with the results

If you can answer every item in sections 1–3 confidently, you have enough information to scope a migration project. If you cannot, that is your discovery scope. Items in sections 4–6 that you cannot answer are stakeholder conversations that need to happen before you start. Section 7 is your go/no-go gate.

Ready to work through this with someone who has done it before?

Schedule a free 30-minute call with Anthony. Bring your checklist answers and get a concrete assessment of your migration scope.