Data Migration
This topic describes how to effectively transition data from legacy systems to the new platform. Additionally, the topic covers data synchronization between Salesforce org. and Platform org. Overall, this topic serves as a functional guide for efficient data migration while minimizing risks and ensuring data accuracy.
Data Migration Preparation
Identify Data to be Migrated: Decide which objects and records (e.g., Agreements, Accounts, documents) need to be migrated. This is typically owned by the customer, and it's important to analyze your legacy contract portfolio to determine the optimal subset for conversion (active contracts, renewals, etc.).
Data Cleansing: Cleanse legacy data before migration to ensure quality, validity, and completeness. This step is crucial for a successful migration.
Create Data Templates: Use Excel templates for each object, ideally exported from Salesforce Data Loader. Identify required fields and relationships to dictate migration order (e.g., Users → Accounts → Agreements → Documents).
Best Practices
Data Mapping: Focus on mapping legacy data to CLM objects. Use sample mapping templates and metadata setup tables for reference. Ensure data transformation is considered to match CLM field type and definition.
Pre-Migration Checks: Validate timezone settings, turn off email deliverability, and disable workflow rules/triggers during migration.
Post-Migration Validation: Create custom reports, spot check data, review exception reports, and use Conga RLM Query Console queries for validation.
Error Handling: Use the migration tool's error logs and reports to correct and reload failed data.
Reverse Data Sync (Advantage Platform to Salesforce)
Limitations: Custom objects mapped to tables (except agreement line-items) cannot be reverse-synced to Salesforce due to platform limitations.
Setup: Establish IdP, configure API connections, and follow the Data Sync instructions in the Admin Console.