I. Access Path

[Admin Console] > [CRM Management] > [Data Maintenance Tools] > [Batch Data Processing]

Notes: 1. The Batch Data Processing tool does not support duplicate checking; 2. The maximum file size for single import is 100MB; 3. The tool does not trigger workflow-related logic (including Business Rules, Approval Processes, and Pipelines); 4. Since the tool bypasses business logic validation, use with caution for operations involving complex business rules.

II. Data Import

Compared to frontend import functionality, batch import has no restrictions on data volume or frequency. It performs only metadata-level validation (without executing frontend business logic), skips duplicate checking, avoids triggering approval/workflows, supports system field imports, and enables master-detail relationship imports. This solution is designed for rapid bulk data loading, primarily for data initialization scenarios.

2.1 Upload Files

1. Select the target object for import
2. Choose import mode (CSV format only). Options are:
   • Add New Records
   • Update Existing Records (When updating Related Teams records, the system considers a field empty only when all Related Teams columns are blank. Otherwise, it will overwrite existing values.)

1. Select record identification method: Unique ID, Primary Attribute (may not always be unique), or any designated field.

Review field format specifications before importing (ensure data complies with standard formats to prevent import failures).

1. Upload CSV files per template requirements (since the tool bypasses business logic validation, verify field compatibility manually to ensure proper system mapping).

2.2 Field Mapping

The system auto-matches file fields with CRM object fields, with manual adjustment options. Unmatched fields can be manually mapped to reduce dependency on standard templates.

For fields with uniqueness requirements, specify matching rules via Primary Attribute/ID/custom unique identifiers.

Custom mapping rules reconcile header name discrepancies between source files and system forms.

Monitor import status and success rates on the Batch Processing dashboard. Failed imports allow downloading error reports or restarting tasks.

Note: Batch-processed data modifications are logged as “System” actions without batch tool identifiers.

III. Data Export

Compared to frontend exports, batch export removes volume/frequency limits, skips frontend business logic (metadata validation only), supports scheduled exports, external system transfers (Aliyun OSS/FTP), and master-detail relationship exports - providing flexible data backup solutions against loss.

Choose between full-object exports (all CRM business objects) or selective object exports.

3.1 Full-Object Export

1. Select export method and complete required fields
2. Optionally include voided records
3. Choose export timing (immediate or scheduled)

Scheduled exports support frequencies: One-time/Daily/Weekly/Monthly with execution timing.

3.2 Object-Specific Export

### 3.2.1 Export Configuration 1. Single-object selection with related object inclusion 2. Destination: Local/Aliyun OSS/FTP 3. Options: Include voided records and/or record IDs 4. Timing: Immediate or scheduled

3.2.2 Filter Settings

1. Select target fields
2. Apply filters: “All Records” or custom conditions

IV. Object Deletion

1. Single-object selection only
2. Scope: Full deletion or filtered records
3. Timing: Immediate or scheduled

Critical Notes: 1. This action permanently destroys data without recovery options! 2. Password verification is required for security.