Operelio vs Salesforce Data Import Wizard

Operelio's saved mappings carry your work from file to file, and ready-made ones cover sources such as LinkedIn Sales Navigator, Apollo and Eventbrite. Columns can merge into one field or split into several, and any field can take a fixed value.

We found no cleaning step in the wizard's docs, so the file must be ready before you start. Operelio dedupes it, fixes formats and runs the free email quality check first. On Starter and up, verification checks whether each mailbox can receive mail, at one credit per address checked.

Before you push, Operelio's report shows what will happen to every row. The wizard shows the result after the import, in its Recent Import Jobs list.

The report checks each row against your org's records and fields and gives the reason for each row not sent or refused. Where one email matches several records, the most recently updated one is written to. A push you start by hand waits for you to confirm. See CRM imports.

Salesforce's docs say that for records added by the import tools or the API, no alert is shown and the record is not saved where a duplicate rule applies.

Operelio writes through the API, so its push follows the same rules. Its report also flags new rows that look like an existing lead or contact by name and company, so you see them before the push, not in the results.

The wizard imports only when you start it. An Operelio trail picks up each new file on arrival or on a schedule, then runs your saved mapping, cleaning steps, checks and the push.

Each trail's folder takes files by upload, by email or through the API (Pro and up), and email-in can be limited to senders you allow. You choose how much runs on its own: approve every push, or let clean runs push by themselves. A run that would change a filled-in Salesforce value always waits.