Known behavior of Data Loader
This reference lists the known behaviors and limitations of Data Loader, including supported file formats, size limits, job submission constraints, and data mapping capabilities.
-
Zuora recommends that you retain the letter case of all column headers in the CSV template. If you modify the header letter case, Data Loader might not recognize the fields correctly, which can cause upload or validation errors.
-
For all custom fields, Data Loader automatically appends the
__csuffix to the CSV header. For example,displayName__c. If multiple custom fields share the same display name, Data Loader also appends the field's API name to the header. For example,displayName__c (apiName)to ensure that each column name is unique.This feature also supports
__cfields in field mapping and auto-mapping when the source and target field names match. -
Data Loader supports import, update, and delete operations for Attributes and Context. For Context, if a Context with the same
objectTypeandobjectKeyexists, the request updates its attributes and retains its Id. If no matchingobjectTypeandobjectKeycombination exists, the request creates a new Context with a newly generated Id. -
Data Loader supports trailing spaces in custom field values. Text fields retain values exactly as entered. Include or exclude any intended spaces in your upload file.
-
Data Loader supports CSV files that are encoded in UTF-8 format. UTF-8 encoding supports a wide range of characters and languages and enables smooth data integration in Data Loader.
-
The maximum supported file size is 300 MB. Data Loader does not accept files that are larger than 300 MB. Keeping file sizes within this limit helps ensure stable and efficient processing.
-
Data Loader accepts a maximum of five jobs at a time. This limit helps manage backend resource allocation and maintain performance. Consider this limit when you plan and schedule data migration jobs.
-
The first row of the CSV file must contain column headers.
-
Data Loader supports one-to-one field mapping. You can map each field in the CSV file to the corresponding field in the target object to create a structure similar to the previous system.
-
The import process is easier when the file structure resembles the object structure in Zuora. Zuora recommends that you import data with the built-in templates. Data Loader automatically maps the fields, and you can modify the field mappings to suit your requirements.
-
Data Loader supports acceptable data formats at the API level for accurate data migration. Expanded date format support is planned for future releases to better accommodate user-specific preferences.
-
Data Loader retains the Uploaded, Records Successful, and Records Failed files for a period of 12 months from their creation date.
-
Data Loader supports Billing and Payments objects for Z Billing. It does not support Zephr, Payment Methods, and Z-Revenue objects.
-
Data Loader supports dynamic templates. Dynamic templates allow you to customize data import formats based on the tenant-level permissions that are enabled. Dynamic templates include the following:
- Multiple Organizations label fields on Account
- Custom fields
- Netsuite integration fields (for Zuora Billing only)
- Other tenant-level permissions such as Multi-Currency, Invoice Settlement, etc.
-
The job fails if the uploaded CSV file contains a byte order mark (BOM). Upload the CSV file without the BOM and submit the job.
-
When you clone an existing job inData Loader, the following parameters are retained:
- Object: The source object from the original job is retained.
- Name of the Job: The name of the original job is retained. However, you can modify this field as needed.
- Field Mapping: If the columns in the uploaded CSV file are unchanged, the existing field mapping is retained. If any columns in the CSV file are modified, review and update the field mapping.