---
title: Rejoining the contact management database
related:
  - https://docs.kentico.com/13/on-line-marketing-features/configuring-and-customizing-your-on-line-marketing-features/separating-the-contact-management-database.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

> **Info:** **Enterprise license required**
>
> Features described on this page require the **Kentico Xperience Enterprise** license.

The following steps describe how to return separated contact management database objects and data back to the application's main database.

> **Warning:** **Warning**
>
> - It is strongly recommended to backup both of your databases before starting the procedure.
> - The databases will be unavailable while the rejoining is in progress. so your website will not work correctly. Run the process at a time when no visitors or editors are accessing the websites in the system. If your site is running live, we recommend taking the front-end application down manually until the database rejoining is complete.

1. Open the **System** application.
2. Select the **DB separation** tab click **Join contact management DB with main DB**.
   - The **Database join** wizard starts.
3. Click **Disable tasks**.

   > **Info:** You need to prevent all [scheduled tasks](https://docs.kentico.com/13/configuring-xperience/scheduling-tasks.md) in the system from running, because the databases will be unavailable during the joining process. If a task is currently being executed when you click the button, the disabling action waits until the task is finished. The tasks will automatically be enabled again after the databases are merged.

   ![Disabling scheduled tasks before joining databases](https://docs.kentico.com/docsassets/13/rejoining-the-contact-management-database/joining_databases.png "Disabling scheduled tasks before joining databases")
4. Click **Next** to continue. The wizard displays a log while the database operations are being performed.

   > **Info:** When the process is successfully finished, all tables and data from the dedicated contact management database will again be a part of the application's main database. If you leave the **Delete separated database** option checked in the final step, the separated database is completely removed from the server.
5. Click **Finish**.
   - The system brings all websites back on-line and enables the inactive scheduled tasks.

Completing the wizard automatically deletes the **CMSOMConnectionString** connection string key from the Xperience administration project's _web.config_ file.

You _**need to manually delete**_ the additional connection string for the separated contact management database from your live site (MVC) project's _web.config_ file. The same applies for any additional [web farm](https://docs.kentico.com/13/configuring-xperience/setting-up-web-farms.md) instances that may be running your application (either for the live site or the administration).

> **Note:** **Rejoining databases on Microsoft Azure SQL**
>
> If your contact management database was hosted on [Microsoft Azure SQL](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-technical-overview), you need to manually perform the following steps after you rejoin the database:
>
> - Move data from the original separated database to the joined database. The process does not move the data, it only re-creates the required database structure.
> - Delete the separated database.