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 from Proposals to Documents

Where once you relied on TinderBox Proposals, now you’re getting the job done in Conga Collaborate Documents.

Migrate your Conga Collaborate document records from the Octiv Proposal object to the Octiv Document object.

The Octiv Document object provides more flexibility in creating documents and will be the object supported and upgraded in future managed package releases. The Octiv Proposal object will not be removed for legacy customers, but updates will not be made to it going forward

Pre-Migration Preparation

There are a couple of things that you must check before migrating your proposals:

  1. If you have created custom fields on the Octiv Proposal object, make sure that you create those same fields on the Octiv Document object
  2. Check that your users have permissions to Read and Write to the Octiv Document object and also that they have Read/Write permissions on all the fields on the Octiv Document object

Export Octiv Proposal data

You can use whatever data loader tool you like, but we recommend dataloader.io. The instructions below apply specifically to dataloader.io, but also work with Salesforce Data Loader with some slight tweaks due to the different user interfaces.

  1. Click New Task, then select Export
  2. Search for and select Octiv Proposal
  3. Click Next
  4. Add filter criteria. If you have a large volume of Octiv Proposal records, use filter criteria to run the migration on a batch of test records to make sure you complete the process correctly before migrating your entire set of records. Some suggestions for filter criteria:
    • Document Status
    • Created Date
    • Related Opportunity Stage
  5. In the left-hand field selector panel, choose all Octiv Proposal fields
  6. Click Next
  7. Click Save & Run
  8. After the job is finished, save/download the export file

Prepare Export File for Creating Octiv Documents

  1. Open the export file you created in the Export Octiv Proposal data section
  2. Copy the values in the column Created By ID
  3. Add a column to the right of Created By ID
  4. Paste the values copied in step 2 into the new, empty column
  5. Rename the column Owner ID
  6. Save this file as a CSV

Import Octiv Documents via dataloader.io

  1. In dataloader.io, click New Task, then select Import
  2. Select the Insert operation
  3. Search for and select Octiv Document
  4. Click Next
  5. Drag and drop the CSV file from the Prepare export file for creating Octiv documents section, or simply click Upload CSV and select the file from your computer
  6. Find Proposal Name under Source Header, and click Select under Salesforce Field
  7. Select Document Name. If you have created custom fields on either the Octiv Proposal or Octiv Document object, ensure that those columns in the CSV are mapped to their corresponding fields on the Octiv Document object
  8. Click Next
  9. Click Save & Run
  10. Verify that Documents were properly created by refreshing the report from the Export Octiv Proposal data section.

(Optional) Delete Octiv Proposals via dataloader.io

Migrating Octiv Proposal records to Octiv Document records does not delete the old Proposal records. If you wish to delete these old records, follow these steps:

  1. In dataloader.io, click New Task, then select Delete
  2. Search for and select the Octiv Proposal object
  3. Click Next
  4. Drag and drop the export file you built in the Prepare Export File for Creating Octiv Documents section, or simply click Upload CSV and select the file from your computer
  5. Click Next. The screen asks which column contains the IDs of the records to be deleted
  6. Select the row with Source Header Record ID
  7. Click Next
  8. Click Save and Run

Repeat this process as necessary until you’ve migrated all of your Octiv Proposal records to Octiv Document records.