Salesforce Data Import Plan and Field Mapping
Plan a safe import of contacts or accounts.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan a data import into Salesforce. Source file columns with a few sample rows: [SOURCE_COLUMNS_AND_SAMPLES]. Target objects and required fields: [TARGET_OBJECTS]. Duplicate rules we have: [DUPLICATE_RULES]. Volume: [VOLUME]. Create a mapping table from source column to Salesforce field with type, transformations and notes. Provide a clean-up checklist (trim spaces, standardise countries and states, split names, valid emails, date formats, picklist values), a duplicate check approach, a test import of 20 records, verification of counts after import with arithmetic, and a rollback plan. Never import without a way to identify and undo the batch, such as an import batch ID field. Import into a sandbox first. Warn about owner assignment, automation that fires on import, and emails triggered by imported records. Confirm I have a lawful basis to hold the data [VERIFY], and list questions for the administrator about import tools and limits [VERIFY]. Present a numbered run plan. Keep the run plan to steps one person can follow in order, and tell me the single check that decides whether to proceed after the 20-record test.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.