Microsoft 365 Migration

Migrate a Microsoft Access Database to SQL Server Without the Upsizing Wizard

Ayan MasoodAyan Masood Nov 13, 2026 869 views

Question details

The user needs to understand why the SQL Server migration option is missing from Access Database Tools and how to migrate an Access database to SQL Server or SQL Server Express.

Migrate a Microsoft Access Database to SQL Server Without the Upsizing Wizard
Product
Microsoft Access, SQL Server, and SQL Server Migration Assistant for Access
Device & OS
not provided
Scenario
Move an Access database's tables and data to SQL Server while checking data types and database structure.
Observed behavior
The SQL Server option described in older Upsizing Wizard instructions is not available in Access Database Tools.
Before you start

Check your Access database format and the supported SQL Server versions in the current SQL Server Migration Assistant for Access documentation. Have your database file, target server connection details, and credentials with permission to create or modify the destination database ready.

Solution 1Recommended

Migrate Access tables and data with SQL Server Migration Assistant

Use Microsoft's dedicated migration tool when older instructions refer to an Upsizing Wizard that is no longer available.

Microsoft removed the Access Upsizing Wizard starting with Access 2013. Its absence from Database Tools is expected in newer versions; it does not mean SQL Server migration is unavailable.

SQL Server Migration Assistant for Access, commonly called SSMA, assesses and converts database objects and migrates data. It does not turn Access forms, reports, or VBA code into a SQL Server application.

1
Install SSMA for Access

Open Microsoft's current SQL Server Migration Assistant for Access documentation and follow its download and installation instructions. Check the listed prerequisites, including any required Access database provider.

2
Create a migration project

Launch SSMA for Access and select File > New Project. Choose the target SQL Server version supported by your installation, then use Add Databases to select your Access .accdb or .mdb file.

3
Assess the source database

In Access Metadata Explorer, select the database or tables to migrate and run Create Report. Review conversion warnings and unsupported objects before proceeding.

4
Connect to the destination

Select Connect to SQL Server and enter the target server or SQL Server Express instance, authentication details, and destination database. Check the schema mapping so the selected Access objects are assigned to the intended destination.

5
Review data types and convert the schema

Open the project's type-mapping settings and review how Access fields will map to SQL Server columns. Choose suitable types and lengths, including varchar for non-Unicode text or nvarchar when Unicode support is needed. Select the source objects in Access Metadata Explorer and run Convert Schema.

6
Load the schema and migrate data

Review the converted objects in SQL Server Metadata Explorer and use Synchronize with Database to create them on the server. Then select the source tables in Access Metadata Explorer and run Migrate Data. Review the migration report for failed rows or conversion errors.

7
Validate the migrated database

Open the destination in SQL Server Management Studio and compare table row counts and sample values with Access. Inspect primary keys, foreign keys, relationships, indexes, null handling, and text lengths; resolve any differences before switching users to the new database.

8
Reconnect an Access front end if needed

If users will continue working in Access, open the Access front-end file and use External Data > New Data Source > From Other Sources > ODBC Database, or the equivalent ODBC Database command in your version. Choose the option to link to the data source, select the SQL Server connection, and test queries, forms, and reports against the linked tables.

Migrate Access tables and data with SQL Server Migration Assistant
SQL Server Express is also a possible destination: Use a SQL Server Express instance supported by your SSMA version. Check the database-size and resource limits for your Express release before migration; moving the data does not automatically make every Access query or application feature compatible.
Free Microsoft Office alternative

Use WPS Office for Documents and Spreadsheet Exports Around Your Migration

WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation work alongside your database migration. Its familiar interface and Microsoft Office file compatibility help you move existing files into your workflow with minimal disruption. WPS does not replace Access or migrate databases to SQL Server.

Review tabular data exported from Access or SQL Server to supported spreadsheet files.Work with Microsoft Word .docx, Excel .xlsx, and PowerPoint .pptx formats.Use a familiar interface for migration checklists, validation summaries, and project reports.Keep routine Office tasks in a lightweight suite while using Microsoft tools for database migration.
microsoft office alternative - wps office

Frequently Asked Questions

Why is there no SQL Server option under Access Database Tools?

Older instructions refer to the Upsizing Wizard, which Microsoft removed starting with Access 2013. Use the current SQL Server Migration Assistant for Access rather than looking for that command in Database Tools.

Can I migrate an Access database to SQL Server Express?

Yes, provided your SSMA version supports the target SQL Server Express release. In SSMA, select Connect to SQL Server and enter the Express instance details. Check your Express release's database-size and resource limits before moving the data.

Should Access text fields become varchar or nvarchar?

Review the project's type-mapping settings before running Convert Schema. Use nvarchar when Unicode characters must be preserved; varchar may be suitable for non-Unicode text. Also verify column lengths and test representative values for truncation or character changes.

Will SSMA migrate my Access forms, reports, and VBA code?

No. SSMA focuses on database schema and data migration, not converting the entire Access application. You can retain Access as the front end by linking to SQL Server tables through External Data > ODBC Database, then testing and adjusting queries, forms, reports, and VBA as needed.

What should I check after the migration finishes?

Review SSMA's migration report, then open the destination database in SQL Server Management Studio. Compare row counts and sample data, inspect keys and indexes, verify relationships and data types, and test any Access front end against the linked SQL Server tables.