Migration Steps of Conga Composer Data
Raptbot Technologies Private Limited
Elevate Your Business with Raptbot: Your Premier Salesforce Partner for Innovation, Integration, and Unmatched Expertise
(From One Salesforce Environment to another Salesforce Environment)
There are numerous tools available in the market for migrating metadata; however, transferring the actual data, particularly in the case of Conga, can be challenging. To simplify the process, follow these step-by-step instructions to successfully migrate the following items: 1. Conga Clauses
2. Clause Types
3. Clause Bundles with Bundle Clauses
4. Conga Templates
5. Conga Queries
6. Conga Solutions with Parameters and queries
Migrating Conga components effectively in Salesforce involves a series of structured steps. Using Salesforce Inspector or Data Loader streamlines the process, enabling you to query and insert records seamlessly. Below is a comprehensive guide for deploying Conga-related objects and their dependencies.
Step 1: Migrate Clause Bundle
Export Clause Bundle from Source Org and import in Target Org using the below query.
SELECT Id, Name, APXT_Redlining__CFS_QuickStart_Example__c, APXT_Redlining__Description__c?FROM APXT_Redlining__Clause_Bundle__c
Note: The following fields are auto-populated upon insertion:
Step 2: Migrate Conga Solution
Export Conga Solution from Source Org and import in Target Org using below query.
SELECT Id, Name, APXTConga4__Button_body_field__c, APXTConga4__Button_Link_API_Name__c, APXTConga4__Composer_Parameters__c, APXTConga4__Custom_Object_Id__c, APXTConga4__Formula_body_field__c, APXTConga4__Formula_Field_API_Name__c, APXTConga4__Is_Quick_Start__c, APXTConga4__Master_Object_Type__c, APXTConga4__Master_Object_Type_Validator__c, APXTConga4__Sample_Record_Id__c, APXTConga4__Sample_Record_Name__c, APXTConga4__Solution_Description__c, APXTConga4__Solution_Weblink_Syntax__c, APXTConga4__Weblink_Id__c FROM APXTConga4__Conga_Solution__c
Step 3: Migrate Conga Query
Export Conga Query from Source Org and import in Target Org using the below query.
SELECT Id, APXTConga4__Description__c, APXTConga4__Name__c, APXTConga4__Query__c FROM APXTConga4__Conga_Merge_Query__c
Auto-populated field: APXTConga4__Key__c.
Step 4: Migrate Conga Template
Export Conga Template from Source Org and import in Target Org using the below query.
SELECT Id, APXTConga4__Description__c, APXTConga4__Label_Template_Use_Detail_Data__c, APXTConga4__Master_Field_to_Set_1__c, APXTConga4__Master_Field_to_Set_2__c, APXTConga4__Master_Field_to_Set_3__c, APXTConga4__Name__c, APXTConga4__Template_Extension__c, APXTConga4__Template_Group__c, APXTConga4__Template_Type__c FROM APXTConga4__Conga_Template__c
Auto-populated field: APXTConga4__Key__c.
Step 5: Migrate Clause Type
Export Clause Type from Source Org and import in Target Org using the below query.
SELECT Id, Name, APXT_Redlining__CFS_QuickStart_Example__c FROM APXT_Redlining__Clause_Type__c
Note: APXT_Redlining__External_Id__c is auto-populated upon insertion.
Step 6: Migrate Clause
Export Clause from Source Org and Import in Target Org, Replace Id of this field APXT_Redlining__Clause_Type__c of Source Org with inserted Clause Type of Target Org, After insertion of clause APXT_Redlining__Clause_Configuration__c will auto created in the Target using the below query.
SELECT Id, Name, APXT_Redlining__CFS_QuickStart_Example__c, ?APXT_Redlining__Changes_Require_Approval__c, APXT_Redlining__Clause_Type__c, APXT_Redlining__Guidance__c, APXT_Redlining__Keywords__c, APXT_Redlining__Restrict__c, APXT_Redlining__Text__c, APXT_Redlining__Text_Rich__c FROM APXT_Redlining__Clause__c
1.???? Retrieve APXT_Redlining__Clause_Type__c from the Target Org: SELECT Id, Name
?????? FROM APXT_Redlining__Clause_Type__c
2.???? Replace the value of APXT_Redlining__Clause_Type__c with the inserted Clause Type.
Auto-populated fields:
After insertion, APXT_Redlining__Clause_Configuration__c is auto-created.
Step 7: Migrate Bundle Clause
Export Bundle Clause from Source Org and Import in Target Org, Replace Id of this APXT_Redlining__Clause_Bundle__c and APXT_Redlining__Clause__c and? APXT_Redlining__Clause_Configuration__c of Source Org with inserted Clause Bundle, Clause and Clause Configuration in Target Org using the below query.
SELECT Id, APXT_Redlining__Clause_Bundle__c, APXT_Redlining__Clause__c, APXT_Redlining__CFS_QuickStart_Example__c, APXT_Redlining__Clause_Configuration__c FROM APXT_Redlining__Bundle_Clause__c
Replace the IDs for:
Note: APXT_Redlining__External_Id__c is auto-populated.
Step 8: Migrate Conga Solution Query
Export Conga Solution Query from Source Org and Import into Target Org, Replace id of these fields {APXTConga4__Conga_Solution__c, APXTConga4__Conga_Query__c} with inserted Conga Solution and Conga Query of Target Org using the below query.
SELECT Id, APXTConga4__Conga_Query__c, APXTConga4__Conga_Solution__c, APXTConga4__Alias__c, APXTConga4__Comments__c, APXTConga4__pv0__c, APXTConga4__pv1__c, APXTConga4__pv2__c FROM APXTConga4__Conga_Solution_Query__c
o?? APXTConga4__Conga_Solution__c
o?? APXTConga4__Conga_Merge_Query__c
Step 9: Migrate Conga Solution Template
Export Conga Solution Template from Source Org and Import Into Target Org, Replace Id of these {APXTConga4__Conga_Solution__c, APXTConga4__Conga_Template__c} with inserted Conga Template and Conga Solutions Id from Target Org using the below query.
SELECT Id, APXTConga4__Conga_Solution__c, APXTConga4__Conga_Template__c, APXTConga4__Comments__c FROM APXTConga4__Conga_Solution_Template__c
o?? APXTConga4__Conga_Solution__c
o?? APXTConga4__Conga_Template__c
Step 10: Migrate Conga Solution Parameter
Export Conga Solution Parameter from Source Org and import into Target Org, Replace Id of APXTConga4__Conga_Solution__c with inserted Conga Solutions Id using the below query.
SELECT Id, APXTConga4__Conga_Solution__c, APXTConga4__Name__c, APXTConga4__Value__c, APXTConga4__Comments__c
FROM APXTConga4__Conga_Solution_Parameter__c
o?? APXTConga4__Conga_Solution__c