Legacy Upload
Organizations may have a large number of existing Agreements that are created outside of ICI platform. These are henceforth referred to as Legacy Agreements. Organizations may want to import these Agreements to ICI to leverage its vast capabilities and manage all Agreements within a single platform.
ICI legacy Migration tool helps in migrating these large volumes of legacy Contracts from the Customer system to ICI Application with accuracy and efficiency which helps in creating a central repository. This in turn helps in a shift from Paper base to digitalization.
The highlights of the ICI Legacy Migration Tool are:
- Uploading entities such as Agreements and their respective Teams, Notes, and Commitments in bulk.
- Uploading Associations, Masterdata, User Information and Amendments in bulk.
- Bulk Clause and Template creation, with the power of Attribute/metadata tagging.
- Enhanced validations, including the ability to exclude the specified attributes from being validated.
- Ability to view logs and report of success and failure statuses on legacy UI.
- Record level email notification trigger capability as per customer requirement.
- Reporting capabilities on the uploaded legacy records.
- Email Notifications for batch initiation and completion.
- Support of Peer Association & Linkage types, ensuring no manual work post legacy upload.
- Enabling legacy upload of Agreements with Status as Expired, Terminated.
- Support uploading of files from Sub folder from Task server and blob storage repository.
Important Considerations
- Only an Administrator can perform a Legacy Upload of the entities.
- The absolute path where the Agreements and other entities documents are saved must be accessible by the task service of the ICI instance. This must be ensured while configuring the ICI instance.
- The Data files created in Excel can only have .xlsx extension.
- For Agreements, only .pdf files are supported. For Associations, several file formats such as .pdf, .docx, .doc, .xlsx, .jpeg, .png and .zip are supported.
- Contract types for the Agreements and other entities that you are trying to upload must be present in Published state in ICI.
- To upload any Associations, ensure that the relevant contract type has been added in the Associations tab in the parent contract type.
- An attribute which will always have unique value must be present in ICI so that the relevant value can be used as a Primary Key to map other entities with that Agreement. If such an attribute does not already exist, you must create it. The unique value attribute can be a backend attribute which may not be visible on the UI. However, Agreement Code attribute, though unique, contains a system-generated value that is generated only after an Agreement has been created thus, cannot be used as a Primary Key for the contract type.
- When adding batches for uploading, it is advisable not to schedule too many batches at close intervals and configure schedules to line-up batches to be uploaded at different times to optimize the processing speed.
- Since this is only a provisioning tool, as such any sort of updates to uploaded records are not supported.
Uploading entities using Legacy Upload
You can use the utility to upload the following entities:
- Agreements with Team, Notes, and Commitment
- Amendments with Team, Notes, and Commitment
- Associated Documents (with or without workflow)
- Masterdata (with or without workflow)
- User Information (with or without Extended Attributes)
- Clauses (with or without Extended Attributes)
- Templates (with or without Extended Attributes)
The Legacy Upload tool follows a simple workflow to upload the aforementioned entities.
The workflow for Legacy Upload process at a glance:
S1
Related Topics: Agreement Management | Managing Organization | Managing Users | Managing User Groups | Managing Security Groups | Application Settings | Notification Settings | Currencies | Reasons | Deleting an Agreement | Search Sync |
