Data copied to Contract Management Pro for Legal Service Delivery during migration from Legal Simple Contracts
Summarize
Summary of Data Migration from Legal Simple Contracts to Contract Management Pro for Legal Service Delivery
This content outlines the process and details of migrating contract data from the Legal Simple Contracts application to the Contract Management Pro for Legal Service Delivery within ServiceNow. A migration utility transfers key contract-related tables and data, ensuring continuity of contract management while transitioning to an enhanced platform.
Show less
Tables and Data Migrated
- Contract Type Table: Contract types from Legal Simple Contracts ([snlgcontractstype]) are migrated to Contract Management Pro ([sncmcorecontracttype]). Existing contract types in the target system are not duplicated, and post-migration edits in the source system are not synced automatically.
- Legal Contract Repository: Legal requests for non-disclosure agreements and third-party contract reviews in a "Close Complete" state are migrated from [snlgcontractsrepository] to [snlgcntrepository].
- Contract Document and Revisions: Contracts are also migrated to the Contract Document ([sncmcoredocument]) and Contract Document Revision ([sncmcoredocumentrevision]) tables, preserving document names, storage URLs, versions, and signed contract URLs.
Key Data Migration Details
- Contract Type Attributes: Includes name, active state, and regional domain.
- State Mapping: Contract states are carefully mapped between systems to reflect accurate statuses, including handling of "Terminated," "Amended," "Expired," "Active," and "Cancelled" states based on contract start and end dates.
- Company and Vendor Data: Vendor fields are populated based on company name matches against the core company table. Recommendations or errors prompt manual adjustments if multiple or no matches are found.
- Document Handling: Document names are standardized based on contract type and company name, with external storage URLs and IDs preserved. Document revisions carry version numbers and file types, differentiating between external URL storage and internal attachments.
Practical Implications for ServiceNow Customers
Customers migrating from Legal Simple Contracts to Contract Management Pro should expect a seamless transfer of key contract data, including contract types, contracts, documents, and revisions. Understanding the state mappings and company/vendor field handling is essential for accurate data verification post-migration.
Note that changes to contract types after migration in the legacy system will not reflect automatically in the new system, so managing contract types exclusively in Contract Management Pro is recommended post-migration.
Contract documents and revisions are preserved with metadata and storage details, enabling continuous access to contract files and signed agreements.
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. |