Your Access system still works. Does it need a complete rebuild?
Check the data, forms, queries and reports separately. You may be able to migrate the system in stages.

The workflow illustrates a possible design and is not a client case study.
- List related functions
- Trial migration
- Validate and cut over
Which daily tasks still rely on Access?
An Access system used for years can contain much more than its tables. Staff may rely on queries, macros, month-end reports and small details of how a form works. Include those tasks and external connections in the migration review; reproducing the screens does not necessarily reproduce the work.
Can you move the database and keep the interface?
Microsoft describes migrations to SQL Server that can keep Access as the front end. If sharing data is the main difficulty, assess that option first. Browser access, external customers or a substantially changed process may call for a new interface.
List what one module needs
Use one module for a trial migration, with its related forms, queries and reports. Migrate a backed-up copy in a test environment and compare the results with the old system. For the live move, agree the downtime and read-only period, how records created during the change will be handled and when a return to the old system would be necessary.
Repeat daily and month-end work
Ask regular Access users to repeat their daily work and a month-end run, comparing the important reports. Check keys, dates, empty values, decimal precision and relationships in the migrated data. Acceptance should cover both the historical records and calculations, and the tasks staff still need to complete.
Bring backups and key reports
Bring a backup you have confirmed can be restored, the Access version and a list of users, external connections and essential reports. Explain which work must continue during the move.