Rehearse CRM import mapping with AI before uploading a sales file

Document the intended change first

Have the CRM owner state whether the job creates records, updates existing records or adds associations. Identify the approved source, target object, permitted properties and responsible operator. Do not begin by asking AI to clean every column; first define which changes the business has actually authorized. Work from a minimized schema and fictional examples where possible.

Retain a copy of the original approved file in the controlled location. Keep stable IDs as text so spreadsheet formatting does not silently alter them. Decide which system owns each field and how blank source cells should be handled under the actual import settings. Do not let a model decide overwrite behavior from a column name alone.

Build a mapping and exception table

For every column record source header, target object/property, data type, valid options, unique identifier, transformation rule and sample validation. Show unmapped columns explicitly. Distinguish company associations from contact properties and identify how the intended relationships will be matched. HubSpot documents spreadsheet-to-property mapping, record updates and associations as separate aspects of importing.

In a fictional deal update file, the account domain appears in one column and the deal ID in another. Matching deals by company name could create or update the wrong opportunity. The rehearsal should flag the missing or malformed deal ID and hold that row. It should not repair the identifier by guessing from the deal title.

Reconcile the rehearsal before authorized execution

Produce counts for source rows, valid IDs, duplicate IDs, missing required fields, invalid option values and held rows. Ask the administrator to review current product-specific identifier and update rules. Use an approved non-production environment if available; a written rehearsal is not a substitute for testing actual import behavior. No production upload is part of the AI preparation step.

Before execution, agree on verification and recovery with the responsible operator. After an authorized import, reconcile the actual result report and inspect a sample of changed records and associations. Retain unresolved rows in a separate queue. Do not retry the whole file blindly after a partial success: determine which records were already changed and which still need action.

Review checklist

• Define create, update and association intent.
• Preserve IDs and an original controlled file.
• Map types, options and blank-value behavior.
• Hold ambiguous rows and reconcile counts.
• Verify actual results before any retry.

Source context and limits

HubSpot documentation supports the import and identifier examples. The rehearsal is our proposed preparation method; actual validation, blank handling and recovery depend on the product and chosen import settings.