Skip to content

Data migration tools ​

Learn about common data migration methods and tool selection guidance for the CRM system.

Overview ​

Data migration is a critical step when enterprises switch systems, consolidate business operations, or undergo organizational changes. It involves transferring historical data from a source system to a target system. ShareCRM provides multiple data processing capabilities to help administrators and implementation engineers choose the right migration method based on their scenario.

Core concepts ​

ConceptDefinitionUse case
Data batch processing toolA batch import, export, and delete tool in the Admin Console for large-scale data operationsSystem initialization, large-scale data backup and cleanup
Standard import and exportImport and export features on the front-end object list page with full business logic validationDaily data maintenance, small-batch data updates
Environment management (sandbox and change sets)Sandbox environments and change set mechanisms for migrating configurations and components between environmentsConfiguration migration from development to production

Data migration method comparison ​

ComparisonData batch processing toolStandard import and exportEnvironment management (change sets)
Migration contentObject dataObject dataConfigurations and components
Data volume limitUnlimited (single file ≤ 100 MB)LimitedNot applicable
Business logic validationMetadata validation onlyFull validationNot applicable
Flow triggeringDoes not triggerCan triggerNot applicable
Applicable phaseData initialization, data migrationDaily data maintenanceConfiguration release

Typical data migration process ​

  1. Planning: Identify the data scope, object relationships, and field mappings for migration.
  2. Preparation: Export source system data and format CSV files according to target system requirements.
  3. Testing: Perform a small-scale import in a sandbox environment to verify data integrity.
  4. Execution: Use the data batch processing tool in the production environment to complete the formal migration.
  5. Validation: Check import results and confirm data accuracy and completeness.

Migration considerations ​

  • Pre-configure objects and fields in the target environment before migration.
  • Import master-detail relationship data in dependency order.
  • After migration, perform a data quality check to confirm that key business fields are complete.