A BACPAC file is essentially a ZIP archive with a .bacpac extension that contains both the schema and data from a SQL Server database. It can be stored locally or in Azure Blob Storage and later imported into Azure SQL Database, Azure SQL Managed Instance, or another SQL Server instance.
When you need to archive a database or migrate it to a new platform, exporting to a BACPAC is one of the cleanest approaches available in SSMS.
How to Create a BACPAC File Using SSMS
Step 1 — Connect to your SQL Server instance
Open SQL Server Management Studio and connect to the desired server. In the Object Explorer pane, right-click on the database you want to export.
Step 2 — Open the Export wizard
From the context menu, choose Tasks → Export Data-tier Application.
Quick note on the similar options in this menu:
- Extract Data-tier Application — exports schema only (no data), producing a DACPAC file.
- Export Data-tier Application — exports both schema and data, producing the BACPAC we want.
- Upgrade Data-tier Application — used to upgrade an existing database using a DACPAC.
Step 3 — Start the Export wizard
A new window titled Export Data-tier Application will open. Click Next to proceed past the introduction screen.
Step 4 — Choose the save location
You have two options: save to local disk or save directly to Microsoft Azure. For local storage, select Save to local disk, click Browse to pick a folder and filename, then click Next.
Step 5 — Review the summary
A summary page shows all your chosen settings. Verify everything looks correct, then click Finish to begin the export process.
Step 6 — Export completes
SSMS will show a success indicator for each step as the export progresses. Once complete, click Close and navigate to your chosen directory to confirm the .bacpac file was created successfully.
For large databases, the export can take several minutes. Consider running it during off-peak hours to avoid impacting production performance.