HubSpot
Salesforce
Pipedrive
Intercom
MailchimpStandardize Salesforce data, so picklists accept it, validations pass, and the sync stops erroring.
Salesforce enforces structure through restricted picklists, validation rules, and state and country lists. Insycle standardizes any field in bulk to the values Salesforce accepts, previewed first, then applied automatically as new records arrive.
- Salesforce AppExchange Partner
- Maintained reference data for states, countries, and postal codes
- Preview and sandbox before production
Before · rejected value
Salesforce response
Write failedINVALID_OR_NULL_FOR_RESTRICTED_PICKLIST
Record stops at enforcement
After · canonical value
Salesforce response
Value acceptedMatches the configured picklist option
Ready for the operation
In Salesforce, bad values do not hide, they throw errors.
Salesforce’s strictness is why it works as a system of record. Standardization is how imported, enriched, synchronized, and manually entered data qualifies for the structure already in place.
Free text meets a restricted picklist, and the record stops synchronizing.
A CSV value outside the legal options fails the row during the load.
A validation rule checks a phone or required field and stops conversion.
Territory logic built on postcodes, states, or countries sends variants down the wrong path.
Company suffixes and drifting phone formats weaken duplicate and cross-system matching.
First, count the variants.
Cleanse Data shows any Salesforce field’s complete value distribution, every distinct value and the records behind it. A picklist configured for roughly 150 options can reveal hundreds of stored variants, turning a suspicion into a ranked cleanup list.
The Health Assessment runs the broader sweep across more than 30 issue types, tracks issue categories over time, and routes each finding to the module and template that resolves it.
Names, phones, states, industries, titles, any field, Leads included.
Start with maintained templates or configure the exact values and formats your Salesforce org requires. Save every setup as a reusable template, share it with the team, and combine related templates into an ordered Recipe.
Proper-case names, trim whitespace, and normalize legal suffixes.
Apply the local, national, or plus-prefixed E.164 format your rules expect.
Map variants to canonical picklist values with maintained geographic reference data.
Translate free-text values into approved categories for reporting, routing, and matching.
Explore the full catalog of 60+ chainable functions and regex
Implementation visual: actual Transform Data template mapping country variants to the Salesforce State and Country/Territory Picklists values
Billing Country
U.S.A. → USA
Maintained reference + org mapping
USA → US
Reusable and automatable
Ready
The stuck operation is usually a values problem.
Three failures can look unrelated until the same inconsistent field appears at each Salesforce enforcement point.
Find the fields the validation rules check, then standardize phone formats and required values across the backlog before the bulk conversion runs.
Map free-text states, countries, and other constrained values to the options both systems accept. This page fixes the values; the sync page owns configuration and triage.
Fix the synchronization pathStandardize staged CSV values before the load. Magical Import checks mapped picklist fields automatically and excludes unresolved rows from the import.
Stage the Salesforce importThey are one standards problem surfacing at three enforcement points.
The variants keep coming, meet them where they enter.
Turn each source of inconsistent Salesforce values into a controlled entry point instead of waiting for the next backlog.
Trigger an Insycle Recipe from Salesforce Flow when a Lead or another supported record is created or updated.
Stage, standardize, and validate mapped picklist values before the file reaches Salesforce.
Standardize before importStandardize the values on both sides so the integration carries options both systems accept.
Protect the syncRun templates from hourly to monthly for records and sources that are not handled by a trigger.
Trigger
Lead createdEntry criteria met
Insycle action
Run standardization RecipeCountry · phone · Industry
Salesforce continues
Routing and follow-upReads accepted values
See every before and after, before production.
Preview produces a CSV with every affected Salesforce record and each transformed field’s Before and After values. Adjust the filters or functions, preview again, and run Update only when the file reads correctly.
- Validate the full process in a Salesforce sandbox when preferred.
- Process large updates in controlled, reviewed batches.
- Monitor API usage for each Salesforce connection.
- Keep the Activity Tracker report after every preview and update.
Capture, not one-click rollback: the completed-run report records Before values. When the Insycle Run ID field is configured, Salesforce records can also reference the run that changed them.
Excel with Data Loader, Flow formulas or Apex, and Insycle.
| Requirement | Export + Excel + Data Loader | Flow formulas / Apex | Insycle |
|---|---|---|---|
| Existing backlog | Full round trip, including load-error handling | Built for forward processing within configured automation | Bulk, retroactive, and filtered |
| New records | Repeat the next round trip | Yes, using field- and Flow-specific logic | Salesforce Flow-triggered Recipes plus schedules |
| Function depth | Spreadsheet formulas and mapping tables | Formula language; deeper logic requires development | 60+ chainable functions, regex, and maintained reference data |
| Who can run it | Someone comfortable with Data Loader | Salesforce admin or developer | No code, with admin-inspectable mechanics |
| Picklist alignment | Manual mapping table | Hand-built for each value and automation | Maintained templates plus your org-specific mappings |
| Dry run | The spreadsheet becomes the rehearsal | Test and debug the automation | Full Before/After CSV; sandbox supported |
| Audit | No durable execution receipt | Flow or Apex execution logs | Activity Tracker report and optional Run ID on records |
Developer verification: Recheck Salesforce Flow, validation-rule, State and Country/Territory Picklists, API-usage, and custom-record-type behavior immediately before publication. Keep the native comparison focused on operating model, not editions or transient UI limits.
Straight answers about standardizing Salesforce data.
How do I fix INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST at scale?
The incoming value is not an accepted option for the restricted picklist. Use Cleanse Data to inventory the variants, map them to the picklist’s canonical values in a Transform Data template, preview the full Before and After CSV, and update the backlog. For future imports, Magical Import automatically checks mapped picklist fields and excludes unresolved rows before loading them.
How do I fix state and country sync errors between HubSpot and Salesforce?
Standardize both systems to the values configured in Salesforce’s State and Country/Territory Picklists, including the integration values used by the synchronization. This page owns the field values; the HubSpot-Salesforce Sync page covers field mappings, inclusion rules, and error-queue triage.
Why will my Leads not convert in bulk?
Salesforce validation rules can block conversion when checked fields are missing or formatted incorrectly. Identify the rules involved, standardize those Lead fields in bulk, such as a phone number that must begin with a plus sign, preview the changes, and retry the conversion process.
Can I standardize Leads and Opportunities, not just Contacts and Accounts?
Yes. Transform Data supports Salesforce Contacts, Accounts, Leads, and Opportunities by default. Other standard or custom record types can be enabled for an account by request.
Will bulk standardization hit our Salesforce API limits?
Insycle shows API usage for each Salesforce connection and processes operations in controlled batches. Review the connection’s available quota, preview and segment very large jobs when appropriate, and coordinate any account-specific limits with your administrator or Insycle support.
Common Salesforce standardization jobs.
Align picklists and drain sync errors
Explore Format phone numbers for conversionMeet validation-rule requirements
Explore Standardize job titles and industriesImprove routing, reporting, and matching
Explore Fix values before importValidate picklists before the load
Explore Standardize on Lead creationTrigger an Insycle Recipe from Salesforce Flow
Explore See a field’s variants firstRank the cleanup by record impact
Explore Explore the full function catalog60+ chainable transformations and regex
ExploreThe operations stop failing when the values become a process.
Picklists, phones, states, countries, industries, and titles can follow the same inspected template whether they arrive through enrichment, imports, synchronization, or Salesforce Flow.
“It makes tasks like deduplication, data standardisation, and bulk updates quick and straightforward. Its flexible, rule-based approach allows for customisation without needing technical expertise.”
Charlotte M. · Global CRM Manager · Mid-Market
G2 reviewConnect Salesforce and inspect any field in minutes.
Start with a sandbox or production org, see every value and its record count, define the accepted format, and preview the complete Before and After CSV.
Declare the standard once
A standardization you re-run monthly is a standard you have not declared.
Turn the mapping into a durable definition, then hold every Salesforce record to it automatically as the org changes.
See how teams declare and enforce CRM data standards