Description

For migrating from one server to another, there are two options.

1. Install Merge1 onto the new server, create a new Database, and manually copy all the configurations from the old (legacy) server to the new one. In this scenario, Merge1 is treated as a new setup, and all the collector information has to be created again.  
2. Install Merge1 onto the new server, and connect to the Merge1 database, which will use all the same configuration's as the old server.  No manual setup is needed.
   1. Install the exact same version of Merge1 as the source server.
   2. Disconnect the old server from the DB by disabling the Merge1WebApplicationPool from the IIS.
   3. Connect to the source DB from the new server.

Note:  If you choose option 2, then the same version needs to be installed on the new server, and an upgrade can be performed after the migration.

In scenarios when the legacy server is already in v7, the Merge1 Agent needs to be registered.  See How to register the Merge1 Agent.

After the migration and registering of the new Merge1 Agent, the legacy agent will be visible in the Agent Pools section. This Agent will need to be deleted, leaving the newly registered agent only.

Additional mandatory actions:

1. The file locations such as log’s path, Folder target’s folder path, Import Folders and Quarantined Folders for files-based (Bloomberg, Text-Delimited, Reuter/Refinitiv, Symphony, etc.…) connectors, should be the same that were in your legacy server.
2. For the connectors that require a self-signed certificate for the configurations in the source settings such as (Microsoft Teams connectors (all of them), Yammer, etc.….) will need to be manually Exported from IIS with the private key, and imported into the new server.
3. There should be no failed messages stuck in the Database. Check the existence of the failed messages from the Report section of Merge1 by checking Unprocessed Messages, Target Deliver Failure, Data Acquisition Failure, and from Bloomberg connector only, alongside the previous ones check the Missing Disclaimer Failure and Missing Attachment Failure. This must be checked on all connectors, and if there are some failed messages they must be reprocessed before starting the migration.

Merge1 migration to new server