Area: Episerver Customer-Centric DXP
Applies to versions: Not applicable

Deploying an existing Commerce site

Recommended reading 

This topic describes first-time onboarding deployment of an existing Commerce website to the Integration environment, as part of the Episerver DXP

When is this applicable?
This is an onboarding scenario for an existing site which you want to move to a cloud-based environment for the first time, for further development and maintenance there. In this case you already have a database with content, and you will need to get that restored to the correct application, which will be done by Episerver.

Before you start

This topic uses Visual Studio with the Episerver extensions and publish profiles. However, you can also use other deployment methods.

  • See Requirements for recommended versions of software, tools and services to use when deploying.
  • See Getting started for information needed to deploy.

Note: If not already done, remember to change the default login credentials (admin/store) provided in the Commerce installation, before deploying. See Installing Episerver.

Output and file formats

To deploy from your local development environment, you need to create a set of output files, and provide these to Episerver for deployment to the Integration environment.

A Commerce solution consists of two websites, a front-end site and the back-end Commerce Manager site, and two databases: one for CMS and one for Commerce. So, there will be additional output components compared to a plain CMS site.

1. Creating the output files

To deploy from your local development environment, export the database as a .bacpac file and upload it to the DXP integration environment’s storage account. Episerver support will import it for you.

You can also upload the BLOBs directly (unpacked) to your DXP integration enviroment’s storage account.

Also, you can deploy the code using Visual studio or the deployment tool of your choice to the DXP integration environment.


Open your solution in Visual Studio, and repeat steps 1-4 in this section for the front-end site, and for the back-end Commerce Manager site, to create the output files for the web application. 

Note: For the Commerce Manager site you need to include the Apps folder manually in the zip file.

  1. Right-click on your project and select Publish.

    1. Select Custom
    2. Enter a name for the publish profile.
    3. Click OK.
  2. On the Connection tab:
    1. Select File system as Publish method.
    2. Select a target location for the files.
    3. Click Next.

  3. On the Settings tab:
    1. Select Release for publishing configuration.
    2. Click Publish.

  4. Locate the application files in the target folder you selected in step 2, and zip them using a zip tool of your choice. 


In MS SQL Server Studio, repeat steps 1-4 below for the front-end site database, and for the back-end Commerce Manager database, to create the bacpac output files.

  1. Connect to the database to use.
  2. Select and right-click on the database, and select Tasks > Export Data-tier Application...

  3. In Export Settings:
    1. Select Save to local disk.
    2. Select a target location for the files.
    3. Enter a name for the bacpac file.
    4. Click Next.

  4. After the export, verify the results and click Close.


For the front-end site, follow the steps below to create the output file for the media/BLOB content. 

  1. In Visual Studio, right-click on your project and select Open folder in File Explorer.
  2. Locate the blobs folder under App_Data, and zip the content of the blobs folder using a zip tool of your choice. 

2. Uploading the output files

When you have created the output files, contact Episerver, and follow the instructions provided to upload them to the assigned area. The deployment will then be finalized by Episerver.

Do you find this information helpful? Please log in to provide feedback.

Last updated: Apr 02, 2020

Recommended reading