Migrating Conga Composer from a Sandbox org to a Production org requires manual steps to complete:

  1. Copy your existing Conga Button URLs from your Sandbox instance to add to your Production instance. You will need to manually create a new button in the Production instance and can then paste into it the appropriate button URL from the Sandbox environment.
  2. Recreate all your Reports (including any necessary custom report types), Queries, and custom fields in the Production instance.
  3. Recreate all the Conga Template records in your Production instance. You will also need to upload the appropriate Word, Excel, PowerPoint, or PDF template file to the coordinating Conga Template record in the Production instance. If you do not have the template files saved on your local computer, intranet, etc., you may download them from the Conga Template record in the Sandbox instance.
  4. Save the source code (HTML) from the Conga Email Template records in your Sandbox instance. We recommend saving each Conga Email Template's HTML source code into a .txt file. Create a new Conga Email Template record in the Production instance and paste the appropriate source code from the .txt file from the Sandbox Conga Email Template record into the Production Conga Email Template record.

The Source button (used to access the HTML source code for a Conga Email Template) is only accessible from the Advanced Editor on the Conga Email Template record.

In the Conga Composer button URL:

  • Update all IDs for example, reports, queries, templates, to the Production versions.
  • Update all references to custom fields. Ensure the field has the correct merge field or API name.

Some browsers have a tendency to add spaces when copying or pasting from one org to another. Remove any additional spaces from the Button URL or errors occur when starting Composer.

Migrating form Sandbox to Production Using Third-Party Metadata Retrieval Tools

It is possible to migrate your Composer configuration using third-party metadata retrieval tools, such as Salesforce CLI, sfdc-hardix, or other such DevOps tools. 

In the event that third-party metadata retrieval tools change processes or behaviors, Conga Technical Support is unable to provide troubleshooting assistance with third-party tools. 

Retrieve Metadata

Using your preferred third-party tool, retrieve the following elements:

The following instructions may be used for migrating Conga Composer, Conga Batch, and Conga Trigger solutions. 

 Metadata - Weblinks and Flexipages.

    1. WebLinks - custom Composer buttons defined on Salesforce objects.
    2. Flexipages - pages where custom buttons and Conga Solutions Components are embedded.
  2. Data - Composer records corresponding to custom objects created by Conga. Examples of the custom object data:
    1. APXTConga4__Conga_Template__c
    2. APXTConga4__Conga_Merge_Query__c
    3. APXTConga4__Conga_Email_Template__c
    4. APXTConga4__Conga_Solution__c
  3. Files - Word documents listed as files/attachments on Conga Template records. 

    When searching for the elements above, it is recommended to utilize the value of Conga Keys rather than their hardcoded IDs, as Keys values will not require updating when migrating. 

Export Conga Records and Template Files

  1. Using third-party tools such as sfdx-hardis or SFDMU, retrieve all Conga related records by exporting the CongaComposer data project.
  2. Identify the generated export.json file, which should contain the configuration data in a json format. 
  3. Retrieve all conga related templates by exporting the CongaTemplates data project.
  4. Identify the generated export.json file, which should contain the configuration data in a json format.

Deploy Metadata

Deploy the Metadata, Data and Files retrieved earlier using your third-party tool. 

  1. Import the CongaComposer and CongaTemplates data projects.