Export – Import Data-tier Application 

Exporting a deployed data-tier application (DAC) or database creates an export file that includes both the definitions of the objects in the database and all of the data contained in the tables. The export file can then be imported to another instance of the Database Engine, or to Azure SQL Database. The export-import operations can be combined to migrate a DAC between instances, to create an archive, or to create an on-premise copy of a database deployed in SQL Database.

The export process builds a DAC export file in two stages.

1. The export builds a DAC definition in the export file – BACPAC file – in the same way a DAC extract builds a DAC definition in a DAC package file. The exported DAC definition includes all of the objects in the current database. If the export process is run against a database that was originally deployed from a DAC, and changes were made directly to the database after deployment, the exported definition matches the object set in the database, not what was defined in the original DAC.
2. The export bulk copies out the data from all of the tables in the database and incorporates the data into the export file.

You can save the BacPac file to On-Premises disk or to Azure Storage

I have saved the file locally, you can choose to export all the table schema and object or you can select the one you want to export

Connect to Azure SQL Database from On-Premises SQL Management Studio

 

Right Click the Database Folder and select Import Data-tier Application

 

Connect to Azure Account , provide the database name and choose from the Azure Database Settings

After the Successful import , you can see the database in Object Explorer.In case you get an error , you have to rectify the error by creating a new bacpac file and try to import again. To read on how to Import a BacPack file explore https://msdn.microsoft.com/en-us/library/hh710052.aspx