Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

download

Migrating Templates

Migrating templates enables you to move templates, and their referenced clauses, from one Salesforce org to another.

Warning:

Close all Microsoft Office products before running a migration.

Migrating Templates and Universal Unique IDs

Universal unique identifier (UUID) fields of the agreement templates, clause templates, and term exceptions in Contract Management support the functionality available with the X-Author Migration Manager.

The UUIDs help provide the ability to update and migrate templates from one org to another. These IDs are unique and once an ID is assigned to a template or term exception object record, it cannot be changed.

To use the templates with the UUID field, you must have X-Author Contracts 7.0 or higher.

Prerequisites

You must have upgraded your source org templates.

Also if there are any schema changes or master data changes that have been made in a source org, they should be rolled out to the target org before migrating. For example, Term Exceptions are lookups from Template object and master records must exist in the target org before migration.

To migrate templates between orgs

  1. Go to the Windows Start menu and select Apttus > X-Author Migration Manager.
  2. Select Create a new migration configuration and proceed to Step 3.- OR -Select Use an existing migration configuration, click to browse to and open an existing upgrade XML file from a previous migration, and proceed to Step 6.
  3. Click Next, select Migrate Templates from one Org to another and click Next.
  4. In the Source Org panel, click Authorize to display the Manage Connections window.
    The listed available connections are those you have already configured on your machine, via either X-Author Migration Manager or X-Author Contracts
  5. Click Connect to choose the source org.

    - OR -

    Enter a new connection name and Login URL and click Authorize.

    If the above action is successful, the Manage Connections window closes and returns you to the X-Author Migration Configuration Wizard. If you do not connect successfully, verify that you have entered the correct username and URL. If the orgs do not have the required version of Contract Management installed, a message is displayed indicating that you must update your org before the migration process can be run.

  6. In the Target Org panel, click Authorize to display the Manage Connection Window.
  7. Click Connect to choose the target org.

    - OR -

    Enter a new connection name and Login URL and click Authorize.

  8. (Optional) Select Show mapping of fields page, and click Next to display the Mapping Fields page. If you choose not to show mappings, the default mapping of known fields will be used. The Map field page displays the header-level Template fields for the source and the target orgs. It includes the name of the field and what type it is. Use the Remove Mapping link to remove default mappings (not recommended).


  9. Click Next to display the Template Filter page.
  10. Using the header-level Template fields for criteria, create expressions to filter which templates are included as part of the migration process.
    Note:

    You must include at least one filter and can have up to a maximum of six filter rows. The relationship between the rows can only be AND. This means additional rows will make the results more restrictive. The operators (not equal to, includes, contains, etc...) are contextually based on the field you select.

  11. Click Next to display the Filter Criteria result page and review the templates and clause templates to be included in the migration. For those templates that reference them, click [+] to display the child and grandchild clauses that are automatically included in the migration. Select a template to display its properties. Click Back to make any necessary changes to your filter criteria.
  12. Click Next to display the Migration Summary page.
  13. Click Save to save this migration configuration for future use. This does not save the org details or login credentials.
  14. Click Finish to begin the template migration.
    The migration runs and displays the progress for each template that is updated.
  15. Log in to the target org to confirm all templates were migrated as expected. Consult the log file for details or to troubleshoot templates that were not successfully migrated.