Data copied to Contract Management Pro for Legal Service Delivery during migration from Legal Simple Contracts
Summarize
Summary of Data copied to Contract Management Pro for Legal Service Delivery during migration from Legal Simple Contracts
This document explains the migration process that transfers data from Legal Simple Contracts tables to Contract Management Pro for Legal Service Delivery tables. It outlines which tables and data fields are migrated, how data mappings are handled, and key considerations during the migration to ensure data integrity and usability within Contract Management Pro.
Show less
Tables and Data Migrated
- Contract Type Table: Contract types from Legal Simple Contracts are copied to Contract Management Pro. Existing contract types in the destination are not duplicated, and changes to the original contract types after migration do not sync automatically.
- Legal Contract Repository: Legal contract requests in the "Close Complete" state, such as non-disclosure agreements and third-party reviews, are migrated. Key fields including contract request number, state, contract number, type, dates, and owner are mapped with specific logic to handle state conversions based on contract dates.
- Contract Document and Revision Tables: Contract documents and their revisions are created in Contract Management Pro from Legal Contract data. Document names are formatted based on contract type and company name, with storage details such as external folder URLs and provider information included. Document revisions capture file type, signed contract URLs, versioning, and file attachments.
Key Migration Details and Data Handling
- State Mapping: States from the old repository are carefully mapped to new states in Contract Management Pro based on contract start and end dates to accurately reflect contract status.
- Company and Vendor Fields: Vendor information is populated by matching company names to the Companies table. Recommendations and errors prompt manual review if multiple or no matches are found to maintain data accuracy.
- Document Naming and Storage: Documents and revisions are systematically named for clarity and traceability. External storage details are maintained for signed contracts and revisions.
Implications for ServiceNow Customers
Customers migrating from Legal Simple Contracts to Contract Management Pro can expect an automated utility that transfers essential contract data while applying logical mappings to ensure consistency. Post-migration, manual reviews may be required for vendor assignments and contract type updates. Understanding the state mapping logic and document handling will help customers maintain contract data integrity and continuity in their legal service delivery workflows.
A migration utility copies data from Legal Simple Contracts tables to Contract Management Pro for Legal Service Delivery tables.
| Legal Simple Contracts tables | Contract Management Pro for Legal Service Delivery tables |
|---|---|
| Contract type [sn_lg_contracts_type] |
Contract type [sn_cm_core_contract_type] |
| Legal Contract [sn_lg_contracts_repository] |
Legal Contracts Repository [sn_lg_cnt_repository] |
Contract type table
The contract type table is copied to Contract Management Pro for Legal Service Delivery.
If a contract type already exists in the Contract Management Pro for Legal Service Delivery table, the contract type is not migrated.
| Contract type [sn_lg_contracts_type] |
Contract type [sn_cm_core_contract_type] |
Description |
|---|---|---|
| Name | Name | Name of the contract type. |
| Active | Active | State of the contract type. |
| Domain | Domain | Regional domain. |
Legal Contract Repository table
Legal requests for non-disclosure agreement and third-party contract reviews that are in the Close Complete state are copied to Contract Management Pro for Legal Service Delivery.
| Legal Contract [sn_lg_contracts_repository] |
Legal Contracts Repository [sn_lg_cnt_repository] |
Description |
|---|---|---|
| Contract Request | Contract Request | Contract request number |
| Contract Status | State | The state of the request. The mapping between states in the old and new repository.
|
| Number | Legacy Contract | The contract number from Legal Simple Contracts. |
| Contract Type | Contract Type | Type of contract from Contract Management Pro for Legal Service Delivery table. |
| Contract Start Date | Starts | Start date of contract |
| Contract End Date | Ends | End date of contract |
| Contract Owner | Contract administrator | The administrator of the contract. |
| Company Name | Company Legal name | The Vendor field is populated based on the availability of Company Name in the Companies [core_company] table.
|
| Vendor | ||
| Company Address | None | The Company Address is part of the Vendor details. |
| Country | None | The Country details are part of the Vendor details. |
| None | Contract type model | Contract model associated with the contract type. |
| Legal Contract [sn_lg_contracts_repository] |
Contract Document [sn_cm_core_document] |
Description |
|---|---|---|
| None | Name | Name of the document. The name is in the format "<contract type> for <company_name>." If the contract type is empty, the name is in the format "<contract_number> for <company_name>." |
| External folder URL | URL | URL of the external storage folder. |
| External folder id | External id | ID of the external storage folder. |
| External provider | Storage provider | Document storage provider. |
| Request opened by | Owner | The user who opened the request. |
| None | Contract type | Contract type corresponding to the record. |
| None | Default version | Version of the document revision that is marked as Ready. |
| Legal Contract [sn_lg_contracts_repository] |
Contract Document Revision [sn_cm_core_document_revision] |
Description |
|---|---|---|
| Refer to the newly created document | Document | Revision of the document. |
| None | Name | Name of the document revision. For external storage: The name is in the format "<contract type> for <company_name>." If the contract type is empty, the name is in the format "<contract_number> for <company_name>." For internal storage: The name is in the format <document_name>. |
| None | File type | The type of document revision. For external storage, the document revision type is a URL. For internal storage, the document revision type is an attachment. |
| Signed Contract | URL | The signed contract is available at the external storage URL. |
| External file ID | External id | ID of the external file. |
| None | Version state | The document revision number, which is set to 1 initially. |
| Document | Document | The file in the document field is copied to the newly created revision record. |