Convert an Access MDB Database to SQL Server in the Correct Order
Question details
Determine the correct sequence for converting an Access MDB database to ACCDB and migrating its data to SQL Server.
- Product
- Microsoft Access and Microsoft SQL Server
- Device & OS
- not provided
- Scenario
- A user wants to modernize an MDB database while keeping an Access application connected to its data.
- Observed behavior
- The desired result is a tested ACCDB application linked to tables hosted in SQL Server.
Work on a copy of the MDB file and identify its tables, linked data sources, and application features that need testing. Confirm that you have access to the target SQL Server database and the permissions needed to create tables and migrate data.
Convert the MDB, migrate its tables, and relink Access
Use this sequence to separate the file-format conversion from the SQL Server migration and verify the application at each stage.
Converting to ACCDB, splitting an Access database, and migrating tables to SQL Server are separate operations. A standard split creates an Access back end; it does not migrate data to SQL Server.
Open the MDB copy in Microsoft Access, then select File > Save As > Save Database As > Access Database to create an ACCDB file.
Open the new ACCDB and test its forms, queries, reports, and VBA code. Update any features or references that do not work as expected before migrating the tables.
Open SQL Server Migration Assistant for Access, add the ACCDB as a source, and connect to the target SQL Server. Convert and review the schema, synchronize it with SQL Server, and run Migrate Data.
In the ACCDB, use External Data > New Data Source > From Database > From SQL Server and choose the option to link to the data source. Select the migrated tables through an appropriate ODBC connection. Menu names may vary by Access version.
Open the linked tables and test the application's forms, queries, reports, and data changes against SQL Server. Remove redundant local tables only after the migrated application works correctly.

Work with exported database data in WPS Office
WPS Office is a free, lightweight alternative for everyday document and spreadsheet work, with a familiar interface and Microsoft Office format compatibility for an easier transition. It does not migrate Access databases or replace SQL Server; use it to review data exported to a spreadsheet.

Frequently Asked Questions
Do I need to split the Access database before migrating to SQL Server?
No. The standard Access Database Splitter creates a separate Access back-end file; it does not move tables to SQL Server. You can migrate the tables and then link your Access front end to SQL Server.
How do I convert an MDB file to ACCDB?
Open a copy of the MDB in Access and select File > Save As > Save Database As > Access Database. Open the resulting ACCDB and test its forms, queries, reports, and code.
How do I link Access to the migrated SQL Server tables?
In Access, select External Data > New Data Source > From Database > From SQL Server, choose to link to the data source, and select the tables using an appropriate ODBC connection. The menu wording may vary by version.
When should I delete the original local tables?
Remove redundant local tables only after you have linked to the SQL Server tables and verified that the application and its data changes work correctly.
Can WPS Office migrate an Access database to SQL Server?
No. Use a migration tool such as SQL Server Migration Assistant for Access. WPS Spreadsheets can help you review data exported to a compatible spreadsheet file.




