Demonstration / Planning Example

Access-to-Web Migration: Planning Example

This planning example shows how to review an Access system before moving it to the web. List what staff use, then decide how to test the data, business rules and switch to the new system.

An illustrative planning example, not a documented client deployment or a measured business result.

Discuss Requirements

Example audience

Owners assessing an existing Access application

Illustrative scenario

Consider a business reviewing remote access, maintenance responsibility or a workflow that is difficult to explain. Investigate the installed Access design and deployment rather than assuming all Access applications are insecure or unsuitable for multiple users.

Planning approach

List the tables, relationships, forms, queries, reports, VBA, macros and integrations. Compare keeping Access, changing where it stores data, buying a suitable tool or rebuilding selected tasks in a browser. Before a rebuild, agree how to map and check the data, who can use it, who signs off and how to recover if the switch fails.

If you need help comparing those options, start with an Access conversion assessment. For work that spans Access and other older tools, see legacy software modernisation.

Acceptance checks

  • The chosen option has a documented reason and preserves necessary business rules.
  • A trial import reconciles important relationships, totals and reports, not only row counts.
  • Users can complete agreed normal and exceptional workflows with the intended permissions.
  • Cutover and recovery define one authoritative writer and how new transactions are preserved.

Discuss the requirements for your own project

Describe the workflow, users and decisions you need help assessing. The relevant service page explains the scope to discuss.

Call