Compare complete options, not database labels
Access combines data, an interface and application behaviour. A database server stores and serves data; it does not by itself supply replacement screens, calculations, reports or a user workflow. Write down what needs to be retained before comparing products.
| Option | When to assess it | Questions still to resolve |
|---|---|---|
| Improve the current Access application | Existing forms and staff workflows still fit. | Deployment, data quality, maintenance ownership and unresolved defects. |
| Retain Access with a server backend | The office interface remains useful but data management needs change. | Connections, query behaviour, permissions and regression tests. |
| Dataverse and a Power Platform approach | The workflow is a candidate for Microsoft’s platform tools. | Data compatibility, interface work, licensing, administration and service dependencies. |
| A packaged business application | A supported product already fits most of the process. | Configuration, imports, gaps, reporting, exports and vendor terms. |
| A custom web application | Required roles, workflows or interfaces justify custom implementation. | Business rules, delivery scope, data migration and long-term operations. |
Retention and hybrid options
Review Microsoft’s split-database approach before discarding a useful Access interface. A SQL Server backend with linked Access tables is another documented path. These options retain desktop behaviour rather than automatically delivering a browser application.
Ask which problem each option solves and which it leaves unchanged. A new backend does not remove the need to understand existing reports, code and staff tasks.
What Dataverse changes and what it does not
Microsoft documents moving Access data to Dataverse, with the possibility of continuing to use the desktop client. Data-type compatibility and the required application components still need review. Moving tables is not evidence that all forms, VBA and reports have become equivalent web functions.
Check current platform capabilities and licensing for the proposed design rather than assuming a subscription already owned covers every component. A platform demonstration should use the business’s important normal and exception tasks.
Packaged software or a custom application?
Try a packaged system against representative tasks before committing. Include an inconvenient exception, an important report, a data export and the work needed to correct a mistake. Record gaps as requirements, not a list of features that sound useful.
Custom work deserves consideration when those gaps are important enough to justify building and maintaining them. A Django application is one possible implementation approach; it is not a substitute for an agreed data model, access rules and acceptance examples. Hosting, updates, backups and support remain part of its operating cost.
Questions for a Canadian operating context
If the business has a location requirement for data, define the requirement precisely and check the selected provider, environment, backups and connected services. Microsoft explains how to inspect Power Platform environment regions and its data storage and governance model. A Canadian business address or a server-region label alone does not establish that every data flow meets a contractual requirement.
- Who owns the tenant, hosting account, source code and usable exports?
- Which currencies, taxes, dates, time zones or language requirements does the business actually need?
- Who supplies and approves those rules?
- What are recurring licence, support, storage and change costs?
- How would the business retrieve its information or change provider later?
Use a short decision record
Illustrative example: a small distributor compares a packaged order tool with retaining its Access office interface. The package covers ordinary orders but not one essential pricing rule. The decision record describes that rule, tests the available configuration and prices the remaining gap. It does not assume custom software wins because the existing system uses Access.
Use the workflow review guide to describe the problem, then the Access migration cost guide to compare equivalent scopes. The Access assessment service is the next step when the inventory and options need technical review.
Related reading
Sources and review notes
https://support.microsoft.com/en-us/access/split-an-access-database
https://support.microsoft.com/en-us/access/migrate-an-access-database-to-sql-server
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/migrate-access-to-dataverse
https://learn.microsoft.com/en-us/power-platform/admin/regions-overview
https://learn.microsoft.com/en-us/power-platform/admin/security/data-storage



Comments
Leave a comment
Comments are reviewed before publishing.