HubSpot
Salesforce
Pipedrive
Intercom
Mailchimp
Lead email
Check the direct identity in the Lead population.
First pass
SalesforceIntegrations
Import CSV data into Salesforce, without duplicates, load errors, or Data Loader gymnastics.
Stage the file before it touches Salesforce. AI suggests the mappings, matching finds rows that already exist as Leads, Contacts, or Accounts, and invalid picklist values are flagged before they fail the load. Records arrive associated, campaign-assigned, owned, and ready to use.
- Salesforce AppExchange Partner
- AI mapping reads column names only, not record data
- Compare before you commit
Magical Import · Event leads.csv
Working copy
CSV staged
Cross-object
matches shown
Automatic
picklist check
Read-only
Compare available
CSV rowSalesforce matchStatus
maya@acme.com · “Lead”Maya Patel · Contact ↗Existing
alex@northstar.ioNew LeadCreate
sam@fieldco.comFieldco · Account ↗Associate
Industry: “SaaS-Tech”Not a valid picklist optionBlocked
Inspect matches and errors before importIllustrative layout
The missing layer before Load
The Wizard is thin. Data Loader is raw. Staging changes the job.
The Salesforce Data Import Wizard is built for straightforward files. Data Loader is powerful, but it expects the file, IDs, and field values to be ready. Insycle adds the working layer between the CSV and Salesforce: match, prepare, validate, associate, and compare every decision first, then write to Salesforce once.
Your file becomes a working copy
Your CSV lands in Insycle first, Salesforce is touched once, at the end.
AI suggests Salesforce field mappings and matching criteria from column names and field labels. It does not send record data to the AI provider, and every suggestion remains reviewable.
Records Mode decides whether the job updates existing records, creates only net-new records, or does both. Field Logic decides what happens column by column.
- Update writes non-empty CSV values over existing values.
- Fill writes only when the Salesforce field is blank.
- Overwrite deliberately writes even empty CSV values.
- Append adds to the existing value or supported multi-select field.
Map fields · Salesforce Contacts
CSV columnSalesforce fieldField Logic
work_emailEmailUpdate
employee_countNumber of EmployeesFill
event_notesDescriptionAppend
Update
FillOnly when Salesforce is blank
Overwrite
Append
Existing employee count protectedPer-field decision
Prevent duplicates at the import door
Check Leads, Contacts, and Accounts before your list creates any of them.
A file labeled “new leads” can contain people who already exist as Contacts. Build the Salesforce import path around the objects your org actually uses, then apply ordered matching criteria, email first, then combinations such as name + company or name + phone, with fuzzy options for real-world variations. Proposed matches appear as live Salesforce links while the file is still staged.
For organizations that do not use Leads, import directly to Contacts and Accounts. Records Mode and matching keep the file from creating a Lead-and-Contact pair for the same person.
Contact email
Catch the person who already converted or entered as a Contact.
Cross-object
Name + company
Use a configured combination when the email changed.
Waterfall
Account domain or name
Connect the person to the existing Account without hand-built IDs.
Associate
Match explanation · Maya Patel
CSV row type
Leadmaya@acme.com · Acme Inc.
Contact matchEmail matched
Existing Salesforce record ↗
Maya Patel · ContactAccount: Acme, Incorporated
No duplicate Lead createdMatch shown first
Make the load boring
Fix the values the load would reject, while it is still a file.
Preparation runs the standardization catalog on the staged copy: proper-case names, format phones to the pattern your validation rules expect, map state and country values to Salesforce’s canonical options, and translate a vendor taxonomy to yours. The source CSV stays unchanged.
Validation automatically checks mapped picklist fields against legal Salesforce options. Add your own gates to require an email, exclude test rows, or isolate a segment. Rows with unresolved errors remain excluded instead of failing halfway through the load.
Prepare + Validate · Event leads.csv
First Name
JANE → Jane
Phone
415.555.0184 → +1 415-555-0184
Billing State
California → CA
Industry
“SaaS-Tech” is not a valid picklist option
Invalid rows excludedSalesforce untouched
Arrive configured
Records arrive attached to your Salesforce org, not merely present in it.
Matched to Accounts
Use domain, Account name, external ID, or another field, with configured tolerance for variants such as Inc. and Incorporated. Assign a parent Account during the same staged process.
Added to a Campaign
Add imported Leads or Contacts to an existing Salesforce Campaign and choose the Campaign Member Status before the import runs.
Owned, typed, and tagged
Set owners, separate records by Record Type, and apply a source, segment, or another constant without adding a dedicated CSV column.
Land configured · Contacts
Imported company
Acme Inc.CSV value
Account match
Ignore legal suffixParent: Acme Global
Salesforce outcome
Acme · AccountExisting Account linked
CampaignFY27 Field SummitMember StatusResponded
Association and campaign settings readyReview before Import
Dry run before, template after
Rehearse it read-only. Then make the recurring import repeatable.
Compare creates a read-only CSV with the staged file beside matched Salesforce records: net-new versus existing rows, current values, and proposed differences. It changes nothing.
Save mapping, matching, preparation, validation, association, Campaign, owner, and Record Type choices in a template. The monthly partner list or weekly event export follows the same reviewed process no matter who runs it.
Compare is the safety step. Import applies immediately after confirmation. Magical Import does not provide another post-confirm preview.
Compare · Monthly partner list
RecordCSVSalesforceResult
Maya Patel · TitleVP SalesVP of SalesWould update
Alex Morgan · Employees500750Protected by Fill
Sam RiveraNew Lead, Create
Read-only report readyNo Salesforce changes
The questions Salesforce importers ask
Straight answers about importing CSV data into Salesforce.
Is there an alternative to Data Loader for Salesforce imports?
Yes. Data Loader remains useful when a prepared file and Salesforce IDs are already in hand. Insycle adds a staging layer for imports that need duplicate matching, field-by-field value decisions, preparation, validation, associations, and a read-only comparison before Salesforce is updated.
Why did my Salesforce import fail on picklist values?
A restricted picklist accepts only its configured options, so an unrecognized CSV value can fail during a native load. When a CSV column is mapped to a Salesforce picklist, Insycle checks the staged values automatically, flags invalid options, and excludes unresolved rows before import.
Can I import a list without creating duplicates of existing Contacts?
Yes. Configure the import to check the relevant Salesforce objects and use ordered matching criteria before creating records. That lets a row labeled as a new Lead resolve to an existing Contact, while Account matching connects the person to the right company.
Can I add imported Contacts or Leads to a Salesforce Campaign with a member status?
Yes. For Salesforce Contact or Lead imports, select an existing Campaign and choose the Campaign Member Status as part of the Import action, so membership is created in the same motion.
Can I undo a Salesforce import?
There is no one-click undo, so run the read-only Compare action before Import. After a run, the report identifies created and updated records. Created records can be matched from that report and removed with the Delete action; Salesforce’s Recycle Bin may then provide recovery subject to its retention and permission rules. Updates to existing records require correction or re-import of prior values. The Delete action itself has no preview after confirmation.
The difference is the working layer before confirmation
Data Import Wizard, Excel with Data Loader, and Insycle staging.
| Requirement | Data Import Wizard | Excel + Data Loader | Insycle Magical Import |
|---|---|---|---|
| Duplicate matching | Native identifiers within the supported import path | None; Salesforce IDs are prepared in the file | Ordered and fuzzy criteria across the relevant Lead, Contact, and Account paths, with matches shown first |
| Existing values | One import behavior for the mapped file | Controlled by the operation and CSV values | Update, Fill, Overwrite, or Append per field |
| Cleaning | Limited preparation | Spreadsheet formulas and manual review | Transformation catalog on the staged working copy |
| Picklists and validation | Errors surface through the import process | Rows can fail during load and return in an error file | Picklist values checked in staging; unresolved rows excluded |
| Associations and hierarchy | Supported native relationships | Lookup IDs assembled in the CSV | Configured Account matching and parent assignment in the staged process |
| Campaigns | Configured separately where needed | Usually a separate load | Campaign membership and member status with Contact or Lead import |
| Dry run | No full side-by-side target comparison | The spreadsheet lookup becomes the rehearsal | Compare produces a read-only side-by-side CSV |
| If something goes wrong | Investigate imported records and correct them | Reconcile success and error files | Run report identifies created and updated records; delete created records by list and correct updates |
| Recurring file | Reconfigure the supported import | Repeat spreadsheet preparation | Saved template carries the reviewed configuration forward |
Developer verification: Recheck Salesforce’s current Data Import Wizard, Data Loader, restricted-picklist, validation, Campaign, and Recycle Bin behavior immediately before publication. Keep this comparison centered on the presence or absence of a staging layer, not transient UI labels or limits. Verify the precise cross-object execution path in the production Magical Import build.
Retire the recurring error-file loop
The safest Salesforce import is a process the whole team can repeat.
The file can change every month while the approved mapping, matching, value logic, validation, association, Campaign, and ownership decisions stay consistent.
“We’ve been able to match and merge records using custom rules, and the preview function gives us peace of mind before making changes. You get much more control and transparency.”
Carlos L. · CRM Admin / Developer · Mid-Market
G2 reviewSee the matches before the import
Upload a CSV and find out which records already exist in Salesforce.
Stage the file, inspect proposed Lead, Contact, and Account matches, fix validation errors, and run Compare before importing anything.
Govern what enters Salesforce
Every import is a writer, and imports are where much of the bad data enters.
Define what is allowed through the door instead of cleaning the same patterns after they land.
See how teams govern what enters the CRM