Once you have installed and configured all necessary Conga managed packages into your target org, you can migrate your Clause Library and Orchestrate definitions using the following steps:

  1. Export and import your Clause Library using the Clause Library Migration Utility

    Conga Provisioning must enable this utility in both your source and target orgs. You can submit a case in the Community Portal to request this to be turned on.

  2. Export and import your Orchestrate definitions
  3. Activate your Orchestrate definitions

Manually Migrate the Clause Library between Salesforce Orgs

In some cases, the Clause Library Migration Utility will not work and you will need to migrate your library manually.

Follow the steps below to move the library between orgs. Once the library has been migrated, follow steps 2 and 3 above to move your Orchestrate definitions.

Export Clause Types from Source Org

Begin with the environment that you’re migrating from:

  1. Log in to dataloader
  2. Export the Clause Type object (APXT_Redlining_Clause_Type__c) and include the field's Id and Clause Type Name
  3. Change the Id header on the export file to read “Original Id” and map this to the Original Id field in the destination org

Import Clause Types to Destination Org

Move to the environment that you’re migrating into:

  1. Log in to dataloader
  2. Set up an insert on the Clause Type object (APXT_Redlining__Clause_Type__c)
  3. Map the fields from your CSV
  4. Check that records created in the new environment

Export Clause Categories from Source Org

Begin with the environment that you’re migrating from:

  1. Log in to dataloader
  2. Export the Clause Category object (APXT_Redlining__Clause_Category__c) and include the field's Id and Clause Category Name
  3. Change the Id header on the export file to read “Original Id” and map this to the Original Id field in the destination org

Import Clause Categories to Destination Org

Move to the environment that you’re migrating into:

  1. Log in to dataloader
  2. Set up an insert on the Clause Category object (APXT_Redlining__Clause_Category__c)
  3. Map the fields from your CSV
  4. Check that records created in the new environment

Export Clauses from Source Org

Go back to the environment that you’re migrating from:

  1. Log in to dataloader
  2. Export the Clause object (APXT_Redlining__Clause__c) with fields Id, APXT_Redlining__Clause _Type__c, APXT_Redlining__Text_Rich__c, Name

Import Clauses to Destination Org

Go back to the environment that you’re migrating into:

  1. Open the clause export file from the Export Clause Categories from Source Org step. 
  2. Create a new column labeled “Destination Clause Type Id” and change the other to read “Source Clause Type Id”
  3. Create an additional sheet within the clause export .csv and copy the data from the Clause Type output success file
  4. Use a vlookup to map Clause Type Ids from your destination org into the “Destination Clause Type Id” column in the clause export file
  5. Save the updated file
  6. Login to dataloader
  7. Set up an insert on the Clause object (APXT_Redlining__Clause__c)
  8. Map the fields from your updated CSV
    1. Make sure "Destination Clause Type Id” is mapped to the APXT_Redlining__Clause_Type__c field
    2. Map the Id column to the APXT_Redlining__External_Id__c field (this will be used in later steps)
  9. Check that the records created in the new environment

Export Clause Configurations from Source Org

Note: This only needs to be done for non-default configurations. Default configurations are generated automatically when the Clause records are created.


  1. If you do not want to migrate all non-default Clause Configuration records:
    1. Create a custom text field on the Clause Configuration object. We will populate this and use it as a filter to only export the Clause Configuration records we want
    2. Create a Salesforce tab for the object in your source org (this only needs to be done in the source org). Set up a view with APXT_Redlining__Default__c = false
    3. Use the view from the Export Clauses from a Source Org step to populate the custom field you created with a value on only the Clause Configurations you want to migrate
    4. Log in to dataloader
    5. Export custom clause configurations using the following query:
      SELECT Id, APXT_Redlining__Changes_Require_Approval__c, APXT_Redlining__Clause__c, APXT_Redlining__Default__c, APXT_Redlining__Restrict__c, Name FROM APXT_Redlining__Clause_Configuration__c WHERE APXT_Redlining__Default__c = False AND {YourCustomField} = {TargetValue}
  2. If you are migrating all non-default Clause Configuration records:
    1. Create a Salesforce tab for the object in your source org (this only needs to be done in the source org). Set up a view with APXT_Redlining__Default__c = false. This will just be used to spot check the migration
    2. Log in to dataloader
    3. Export custom clause configurations using the following query:
      SELECT Id, APXT_Redlining__Changes_Require_Approval__c, APXT_Redlining__Clause__c, APXT_Redlining__Default__c, APXT_Redlining__Restrict__c, Name FROM APXT_Redlining__Clause_Configuration__c WHERE APXT_Redlining__Default__c = False

Import Clause Configurations to Destination Org

Since you have uploaded clauses by this point, the system will have automatically generated the default configurations for these clauses. The query from the Export Clauses from Source Org step will have provided you with a CSV of all additional configurations which you created.

  1. Use the success file from your clause import from the Import Clause Categories to Destination Org step to update the Clause lookup on the Clause Configuration records using a vlookup
  2. Verify that no configurations have a True value in the Default field
  3. Upload the CSV to the APXT_Redlining__Clause_Configuration__c object
    1. Map the Changes Require Approval field
    2. Map the Restricted field
    3. Map the Clause lookup field
    4. Map the Id to the APXT_Redlining__External_Id__c field

Export Sub Clauses from Source Org

  1. Log in to dataloader
  2. Run an export using the fields in the following query:
SELECT Id, APXT_Redlining__Clause_Configuration__c, APXT_Redlining__Clause__c, APXT_Redlining__Label__c, APXT_Redlining__Sort_Order__c, APXT_Redlining__SubClause__c, APXT_Redlining__Sub_Clause_Configuration__c, APXT_Redlining__Sub_Clause_Configuration__r.External_Id__c FROM APXT_Redlining__Sub_Clause__c
CODE


Import Sub Clauses to Destination Org

  1. Pull a full export of the Clause Configuration records in your target org
  2. Use a vlookup on the configuration name to update the configuration ID on each sub clause
  3. Pull a full export of your Clause records and use a vlookup to update the Clause lookup on each sub clause to use destination org Clause Ids
  4. Log in to dataloader and set up an insert on the Sub Clause object (APXT_Redlining_Sub_Clause__c)
    1. Map the Clause Configuration ID to the updated lookup column field in your CSV
    2. Map the Sort Order
    3. Map the Clause ID to the updated Clause column in your CSV

Export Alternate Clauses from Source Org

  1. Log in to dataloader
  2. Run an export using the fields in the following query:
SELECT Id, APXT_Redlining__Clause_Configuration__c, APXT_Redlining__Clause__c, APXT_Redlining__Sort_Order__c, APXT_Redlining__Label__c, APXT_Redlining__Alternate_Clause_Configuration__c, FROM APXT_Redlining__Alternate_Clause__c
CODE

Import Alternate Clauses to Destination Org

  1. Create 3 new columns in your export file from the Export Sub Clauses from Source Org step:
    1. Prod Clause Configuration Id
    2. Prod Alternate Clause Configuration Id
    3. Prod Clause Id

  2. Export all Clause Configuration records from prod. Include Id, APXT_Redlining_Label__c, APXT_Redlining_Clause__c, and APXT_Redlining__Clause__r.APXT_Redlining_External_Id__c

    External_Id__c on the Clause object should have the clause Id from your source org, assuming you included that in your clause import in the Import Clause Categories to Destination Org step

  3. Note that both fields are lookups to the Clause Configuration object
  4. Use the Clause import success CSV from the Import Clause Categories to Destination Org step and use a vlookup to populate the Prod Clause Id column with clause Ids from your destination org
  5. Log in to dataloader and set up an insert on the Alternate Clauses object (APXT_Redlining_Alternate_Clause__c)
    1. Map the Alternate Clause Configuration field
    2. Map the Clause Configuration field
    3. Map the Clause field
    4. Map the sort order

 Export Clause Bundles from Source Org

  1. Log in to dataloader
  2. Run an export using the fields in the following query:
SELECT Id, Name FROM APXT_Redlining__Clause_Bundle__c
CODE

Import Clause Bundles to Destination Org

  1. Log in to dataloader
  2. Set up an insert on the Clause Bundle object (APXT_Redlining_Clause_Bundle__c)
    1. Map the sandbox ID field to the External ID field
    2. Map the Name field

Export Bundle Clauses from Source Org

  1. Log in to dataloader
  2. Run an export using the fields in the following query:
SELECT Id, External_ID__c, APXT_Redlining__Clause_Bundle__c, APXT_Redlining__Clause_Bundle__r.APXT_Redlining__External_Id__c, APXT_Redlining__Clause_Configuration__c, APXT_Redlining__Clause__c, APXT_Redlining__Clause__r.Name, APXT_Redlining__Clause__r.APXT_Redlining__External_Id__c, APXT_Redlining__Order__c FROM APXT_Redlining__Bundle_Clause__c
CODE

Import Bundle Clauses to Destination Org

  1. Use the Clause success file from the Import Clause Categories to Destination Org step, the Clause Configuration export from the Import Clause Configurations to Destination Org step, the Clause Bundle success file from the Export Clause Bundles from Source Org step to use vlookups to populate the Clause, Clause Bundle, and Clause Configuration columns on your import CSV using destination org Ids
    1. Pull clause name and Id from destination org, then use vlookups to associate destination org Clause Ids with the proper Bundle Clause records in your CSV
    2. Vlookup configuration ID’s from your destination org, mapping against the parent clause name where the configurations are DEFAULT
    3. For non-default configurations, map against the custom field value you set up in the Export Clauses from Source Org and Import Clauses to Destination Org steps (it is used as an external ID)
  2. Log in to dataloader and set up an insert on the Bundle Clause object (APXT_Redlining_Bundle_Clause__c)
    1. Map Clause Bundle
    2. Map Clause Configuration
    3. Map Clause
    4. Map Sort Order

Export Clause Approver from Source Org

  1. Log in to dataloader
  2. Run an export using the fields in the following query:
SELECT APXT_Redlining__User__c, Id, Name FROM APXT_Redlining__Clause_Approver__c
CODE


Import Clause Approvers to Destination Org

  1. Use a vlookup to update the User Id column with Ids from your destination org
  2. Log in to dataloader and set up an insert on the Clause Approver object (APXT_Redlining_Clause_Approver__c)
    1. Map the User field to the User Id column you just updated

Export Approval Steps from Source Org

  1. Log in to dataloader
  2. Run an export using the fields in the following query:
SELECT Id, External_Id__c, APXT_Redlining__Approver_Name__c, APXT_Redlining__Clause_Approver__c, APXT_Redlining__Clause_Approver__r.External_Id__c, APXT_Redlining__Clause_Configuration__c, APXT_Redlining__Clause_Configuration__c FROM APXT_Redlining__Approval_Step__c
CODE

Import Approval Steps to Destination Org

  1. Use the Clause Configuration export from the Import Clause Configurations to Destination Org step and the Clause Approvers success file from the Import Bundle Clauses to Destination Org step to vlookup the destination org Ids for the Clause Configuration and Clause Approver columns in your CSV
  2. Log in to dataloader and set up an insert on the Approval Step object (APXT_Redlining_Approval_Step__c)
    1. Map Clause Approver ID
    2. Map Clause Configuration ID