Topic
How To Migrate DocGen Package from one Salesforce environment to another.
What does and does not migrate?
Instructions
We recommend the user migration for both environments is a System Admin. This will allow all the correct permissions when checking the migration.
Please review the Documentation below:
1. https://help.nintex.com/en-US/docgensf/Troubleshooting/MigrateDocGenPackages.htm
2. https://help.nintex.com/en-US/docgen/docservices/#docgen-sfdc/Services/manageDDP/MigrateDDPs.htm
3. Unable to Migrate Document Packages from One Environment to Another
Additional Information
Note: Currently, migration is only supported in Salesforce Classic.
- Please vote on our Uservoice page: Lightning Migration
What does not migrate?
- Org-wide emails: These will need to be reassociated on the delivery option as the org-wide email reference Id is different in each org.
- Email templates: These will need to be reassociated on the Delivery Option as the Template Id is different in each org.
- Form Field defaults: These will need to be reassociated to the desired fields.
- Custom Fields: Fields that do not exist in the destination org.
- Note: This is important for DocGen Relationships. If a relationship is filtered on a field that does not exist in the destination org, The migration will fail.
- Salesforce Reports: Reports that do not exist in the destination org. If they exist and have the same name, the migration should be successful.
- Component Group Images: Images that are not publicly linked, will not migrate. Reassociate the Images after the migration.
