The Template Migration Tool helps Formstack Documents for Salesforce customers begin their migration journey by converting Conga Composer document templates into Formstack document templates.
Note: The tool currently only focuses on converting Conga Composer templates, and it only assists with converting template files and mapping fields; no settings or automation configurations are migrated.
How to Use the Template Migration Tool
When Will You See the Migration Tool
The Conga Template Migration Tool will only appear if all of the following conditions are met in your Salesforce environment:
-
Conga Composer is installed in your Salesforce org
-
There is at least one Conga Solution (with templates) available
-
The user has the Formstack Documents for Salesforce permission set assigned
Note: If any of these requirements are not met, the tool will not be shown in the UI.
Automatic Detection of Conga Composer
When you log into the Formstack Documents for Salesforce app:
-
The system automatically checks if Conga Composer is installed in your Salesforce org.
-
If detected, a pop-up will appear at the bottom-right corner of the Formstack Mapping Tab and prompt you with a Call to Action (CTA) to start migrating your templates.
💡 Tip: If you miss the pop-up, you can manually launch the migration tool by clicking the "Migrate Template" button located at the top-right of the Formstack Mapping Tab.
Selecting Templates for Migration
The app scans and lists all Conga Composer templates inside the migration tool. Only supported file types are selectable (see below for supported formats).
-
Select the templates you would like to migrate.
-
Click "Convert Template" to start the migration.
During Migration
Once a request is submitted, you will be notified that it's being processed. New mapping fields will be listed, with "Processing" status during conversion.
After Migration
Upon successful conversion, templates are updated to "Active" status.
- Each newly converted template will also display a "New Template" tag for 24 hours as a reminder for you to review the mapping and configure any additional settings manually.
- Fields that cannot be confidently mapped will be flagged with a "Need Attention" tag to help you identify and correct them.
Important Reminder: the migration tool does not migrate any settings, and field mappings are generated based on best-effort matching. While we aim to map fields accurately, some fields may require manual adjustment. We strongly recommend that you carefully review all fields.
Limitations of the Conga Template Migration Tool
While the Conga Template Migration Tool simplifies the first step in transitioning from Conga Composer to Formstack, it does not handle every aspect of your existing setup. Please review the following limitations before starting your migration:
Unsupported File Types
The migration tool cannot convert the following types of Conga Composer templates:
-
Email Templates
-
Excel Files (.xlsx)
-
PDF Files (.pdf)
-
PowerPoint Files (.pptx)
Only Word (.docx) file templates are supported.
Unsupported Template & Mapping Features
-
Nested tables are not supported. If your Conga template contains nested tables, the formatting and data layout may not carry over correctly.
-
Child relationships (e.g., related lists) may not always be processed accurately. Templates using child objects may require manual reconfiguration after migration.
- Mapping to the User object isn't supported; instead, use a SOQL query to access user information. For details about SOQL queries, please refer to this article (/hc/articles/44592069904531
-
Templates included in Template Groups will not appear in the tool. These need to be manually migrated.
- Signature and write-back tags related to Conga Sign are not supported.
Settings and Automation Are Not Migrated
-
The tool does not transfer any Conga Composer settings, automations, triggers, or integration.
-
No user permissions or security settings are migrated.
-
Template Groups from Conga Composer are not supported.
- If a Conga Solution uses Template Groups, a single Conga Solution containing multiple document files (e.g., several order forms grouped under one solution), the migration tool will not process them.
- Only one file per solution is supported.
Where to Configure Your Document Settings
After using the Conga Template Migration tool:
-
Some settings related to your document setup can be found and configured on the Field Mapping page inside Document for Salesforce.
-
Other settings must be configured in Formstack Documents Core (Doc Core).
Reminder:
The migration tool does not migrate any Conga Composer settings. Additionally, field mappings are auto-generated based on best-effort logic and may not be complete or fully accurate.
Please be sure to:
-
Review your field mappings carefully
-
Manually reconfigure all required settings in both the Mapping page and Doc Core
-
Test your templates thoroughly before relying on them in production
If you run into an issue using the migration tool, please reach out to Formstack Support following the instructions in the Contact Formstack Support article (/hc/articles/44593101346963).