How do I import legacy contracts?

Use the Import Legacy Contracts task to create many legacy contract workspaces at once. A legacy contract refers to a contract that existed in another system before your organization started using Ariba Contract Management Solutions.

To prepare your legacy contract import:

1. Create and publish a blank contract workspace template with no documents or default team members. Your site uses this template to create each legacy contract. There is no legacy contract template in the default configuration.
2. Create a ZIP file with four comma-separated values (CSV) files:
   
   
   • Contracts.csv
   • ContractDocuments.csv
   • ContractTeams.csv
   • ImportProjectsParameters.csv

   
   Each CSV file contains a specific format that your site uses to create a contract workspace for each legacy contract. The attached ZIP file provides an example of a properly formatted import ZIP file with no contract documents.
   
   All configuration CSV files must appear at the top level of the archive ZIP file, and the only subdirectories within the ZIP file must include the documents referenced by the ContractDocuments.csv file.

Next, run the Import Legacy Contracts task:

1. Go to Project Manager > Import Legacy Contracts.
2. Browse for the ZIP file that contains the legacy contracts.
3. Click Import. The Import Legacy Contracts Status page appears.
4. Click Refresh Status to see if the import completes successfully.

Best practices:

• A Contract Workspace template should be created specifically for legacy imports including only tasks which are needed for the legacy contract workflow. Any required tasks from the template being used will be required for publish.
• Import contracts in Published status unless the business requires a workflow to be completed for legacy contracts.

See the Contract Administration Guide for more details on importing legacy contracts.

How do I import legacy contracts?.zip

1000 bytes

For Legacy import errors please refer What are the most common errors encountered during legacy contract import? (ariba.com)

Here are some additional tips related to importing legacy contracts:

• You cannot add tasks to a contract workspace using the legacy contract import operation, but you can create the workspaces using a project template that contains tasks.
• Loading legacy contract workspaces is a time-consuming process. For example, an upload of 7,500 contract workspaces with no added documents or team members takes approximately 16 hours. Because of the time involved, be sure you verify all data before loading it.
• The maximum size for the ZIP file is 100 MB. If the contracts you want to load do not fit in a ZIP file that is smaller than 100 MB, divide the contracts into multiple ZIP files.
• Import legacy contracts can be used to create any kind of contract workspace or contract request. The type of contract created is based on the template specified in ImportProjectsParameters.csv
• Contracts can be imported in Published status by specifying Published in the ContractStatus column within Contracts.csv.
• The import will stop when it encounters the first error encountered. If an error is encountered, check to see if anything else seems to be a problem to reduce the number of iterations required.
• ImportProjectsParameters.csv cannot be renamed in any way. This is the first file the system looks for. Omitting the "s" on the end of the word projects is a common reason for failure.
• Custom fields may be included by creating a column with the system field name. This is not the display name. The field name typically follows the format cus_FieldDisplayNameWithoutSpaces, but this is not always the case. SAP Ariba customer support can verify custom field names if required.

Strategic Contracts > Strategic Contracts Import/Export