Skip down to the research record

Sales data imports: 5 field checks before upload

Quota Forecast Editorial Team · Published · 11 min read

Verify field types to prevent import failures by checking length limits, type conversion, validation triggers, visibility settings, and permission checks. Zoho CRM throws an 'INVALID_DATA' error if the field value length is more than the maximum length defined for that field, according to Zoho.

Verify field types to prevent import failures

Bulk imports fail when data types mismatch system limits. The five critical rules to verify are length limits, type conversion, validation triggers, visibility settings, and permission checks. These checks cover upload constraints as well as field visibility and management.

Length limits are the first check. If a text value exceeds the field's maximum length, the Zoho CRM API returns an 'INVALID_DATA' error. Verify the character count of your source data against the destination field’s maximum length before uploading.

Type conversion rules determine whether existing data survives a field type change. Close supports safe custom field conversions from Choices (single) to Choices (multiple) and from User (single) to User (multiple). Confirm whether your platform preserves existing values when you change a field from text to numeric or single-choice to multiple-choice.

Validation triggers apply rules during record creation or update. API updates may trigger validation logic that rejects records failing specific criteria. Check whether your import method bypasses or enforces these validation rules.

Visibility settings control where custom fields appear. Some fields are hidden from standard views or exports unless explicitly enabled. Ensure the fields you import are visible in the views your team uses for reporting.

Permission checks in Pipedrive govern who can add, edit, or delete custom fields. Verify the API user or service account has write access to all target fields.

Key takeaways for how to verify custom field data types before importing sales data

  • Length limits: Zoho CRM API throws the 'INVALID_DATA' error if the field value length is more than the maximum length defined for that field, according to Zoho.
  • Type conversion: Close allows you to safely change a custom field from type Choices (single) to Choices (multiple) and from User (single) to User (multiple), according to Close.
  • Validation triggers: To trigger Validation Rules during record creation or update through the API, include the apply_feature_execution array in your request body, according to Zoho.
  • Numeric limits: Large integers (Big or BigInt) are large numbers with a max value of 9,223,372,036,854,775,807, according to Microsoft.

A filled reference table of field rules by publisher

The table below lists specific limits and rules for Zoho, Microsoft, Close, and HubSpot. Each row is tied to the publisher that states the rule.

PublisherRule TypeSpecific Limit or Behavior
ZohoText length errorsThe 'INVALID_DATA' error is thrown if the field value length is more than the maximum length defined for that field, according to Zoho.
MicrosoftNumeric value limitsLarge integers (Big or BigInt) are large numbers with a max value of 9,223,372,036,854,775,807, according to Microsoft.
CloseSafe type changesYou can safely change a custom field from type Choices (single) to Choices (multiple) and from User (single) to User (multiple), according to Close.
HubSpotSubscription requirementA Professional or Enterprise subscription is required to use the calculation field type, according to HubSpot.
Quota ForecastImport verification stepOpen your CRM's custom field settings and verify the maximum length and type of the fields you plan to import into today.

Verify these four specific constraints against your import file before uploading.

Understanding numeric and text limits

When preparing a bulk import of deal records, you must verify that your numeric values and file attachments fit within the specific storage constraints defined by your system. Microsoft Dataverse documentation outlines precise boundaries for large integer fields and file storage that directly impact whether an upload succeeds or fails.

For large numbers, Microsoft defines Large integers (Big or BigInt) as large numbers with a max value of 9,223,372,036,854,775,807, according to Microsoft. For values destined for Microsoft Dataverse Large integer fields, check that they do not exceed this maximum. Microsoft also notes that some uses for this type include storage of time stamp values and as unique IDs, as well as numbers larger than 100 billion, according to Microsoft. This distinction matters if you are importing timestamp data or high-volume unique IDs alongside standard monetary values.

File attachments present a different set of limits. Microsoft states that the default Maximum file size is 32 MB, and the largest size you can set by using the designer is 131,072 KB (131 MB), according to Microsoft. Before uploading contract PDFs or proposal documents, check if any file in your batch exceeds the 32 MB default. If your workflow requires larger attachments, you must adjust the designer settings to allow up to 131,072 KB.

Storage size constraints also apply to specific field types. Microsoft specifies that the minimum size is 1 KB and the maximum is 30,720 KB, according to Microsoft.

To verify these limits before your import, open your CRM's custom field settings and confirm the maximum length and type of the fields you plan to use. For Microsoft Dataverse, check Large integer values against 9,223,372,036,854,775,807 and file attachments against the file field's configured maximum: 32 MB by default, adjustable in the designer up to 131,072 KB. Ensure no single attachment exceeds the configured maximum. For unique IDs or timestamps, check values against the destination field's actual limits. These checks prevent failed uploads and ensure your pipeline data remains intact.

Handling type changes and conversions

Before importing bulk data, confirm whether your CRM allows you to modify field types after creation. Close documents specific safe conversion paths for custom fields. According to Close, you can safely change a custom field from type Choices (single) to Choices (multiple) and from User (single) to User (multiple). This specific guidance applies to the "Custom Fields | Close Help Center" documentation. If your import requires expanding a single-select field to accept multiple values, verify that your current field type matches one of these supported transitions.

Close also provides a direct method for editing existing properties. According to Close, you can change the name and type of an existing Custom Field once it is created by clicking the pencil icon on the row of that Custom Field. This action is part of the broader field management capabilities available on the same page. According to Close, you can create, rename, merge, remove, and change types of Custom Fields from this page. These actions allow you to adjust field definitions before or during the import preparation phase. Ensure that any type changes you make align with the data structure in your source file to prevent mismatch errors during upload.

HubSpot offers similar flexibility for certain property types. According to HubSpot, for certain field types, you can also edit the property’s type or options after the property is created. This capability is documented in the "Understand property field types in HubSpot" guide. When preparing a bulk import in HubSpot, check which specific field types support post-creation editing to determine if you can adjust definitions to match your data. If a field type does not support editing after creation, you may need to create a new field with the correct type and map your data accordingly.

Triggering validation during record creation

When you build an API request to create or update records, you can force the system to run its validation logic by adding specific parameters to the payload. In the "Update Records | Zoho CRM API |V8" documentation, the guide states that to trigger Validation Rules during record creation or update through the API, you must include the apply_feature_execution array in your request body, according to Zoho. This parameter acts as the switch that tells the API to respect the validation rules defined in your system rather than skipping them.

If you want to ensure that specific criteria-based rules are checked, you can refine this trigger. The same Zoho documentation explains that when you use the apply_feature_execution array with criteria_validation_rule, the system evaluates all applicable rules, according to Zoho. Zoho API requests using apply_feature_execution with criteria_validation_rule evaluate all applicable rules.

In HubSpot, numeric property values can determine workflow enrollment. The "Understand property field types in HubSpot" guide provides a concrete example of how numeric values trigger actions. It notes that a contact with a value of -2.5 for a number property will enroll in a workflow with the enrollment trigger "Number property is less than -2," according to HubSpot. This demonstrates that numeric field types are not just storage containers; they are active triggers for downstream automation.

HubSpot also offers a specific field type designed for dynamic logic. The same HubSpot documentation defines the Calculation field type as one that stores equations based on properties of associated records, or based on properties in custom equations, according to HubSpot. If your import includes data that should be calculated rather than manually entered, understanding this field type is crucial. It allows the system to derive values automatically, reducing the need for manual validation of those specific numbers during the upload.

Before you execute the import, review your API payload against these specific requirements. Check that your Zoho requests include the validation array and that your HubSpot numeric values match your workflow triggers. This direct check prevents silent failures where data is saved but not processed as intended.

Checking visibility and permission constraints

Before importing, confirm that your custom fields are visible in the interface where you will add records. In Pipedrive, a field visibility option controls whether the field appears when adding new items, such as deals or leads, in their respective add views according to Pipedrive. If this option is not enabled, the field may not be accessible during the record creation process. To make a custom field visible in the table view, click on the gear icon to the right of the table and select the custom field in the “Choose columns” section according to Pipedrive. This step ensures the data is present in the interface you use for verification.

Permissions also gate who can manage these fields. Adding, editing, and deleting custom fields is only available for users with the correct global permissions enabled according to Pipedrive. Verify that your team members have these permissions before assigning them to configure or review field types.

Subscription levels can restrict access to specific field types. A Professional or Enterprise subscription is required to use the calculation field type according to HubSpot. If your plan does not include this tier, calculation fields may not be available for import or configuration.

Export visibility varies by platform. In Close, custom fields are represented as "custom.My custom field": "some value" and are not visible in export according to Close. This means data stored in these fields will not appear in standard export files, so you must verify visibility through other means if you rely on exports for validation.

Action step: Open your CRM’s custom field settings and verify the maximum length and type of the fields you plan to import into today.

FAQ: How to verify custom field data types before importing sales data

What error occurs if a field value exceeds the maximum length?

According to Zoho, the "INVALID_DATA" error is thrown if the field value length is more than the maximum length defined for that field.

Can a single-choice field be safely converted to multiple-choice?

According to Close, you can safely change a custom field from type Choices (single) to Choices (multiple). The documentation also confirms that you can safely change a custom field from User (single) to User (multiple).

Which subscription level is required for calculation fields?

According to HubSpot, a Professional or Enterprise subscription is required to use the calculation field type. This requirement is specific to the HubSpot property field types described in their knowledge base.

How do you trigger validation rules during an API update?

According to Zoho, to trigger Validation Rules during record creation or update through the API, include the apply_feature_execution array in your request body. This mechanism is documented in the Zoho CRM API V8 update records page.

Are custom fields visible in standard exports?

According to Close, custom fields are not visible in export. The documentation notes that these fields, such as "custom.My custom field", are not visible in export.

Sources