One file, two ways: the native import vs Sloose

By hand

Zoho's import takes one main module per upload. For contacts and accounts in one file, its FAQ says to copy the account details out, import them into Accounts, and then import the original file into Contacts. Deals are a third upload, with lookups to the accounts and contacts the first two made.

In Sloose

One import, one file, three modules. The map of the work shows each module the file feeds, and the run writes each row's account, then its contact, then its deal, linked to the records the same row made.

By hand

Each lookup column finds its record one way, chosen when you map it: a record ID, a unique field, the record's name, or an email for contacts. A company spelled another way from the account you imported may not find it.

In Sloose

A deal can link to the account and contact its own row made (rec.Account in a formula), so there is no ID to look up. Where a link has to find a record your CRM already holds, a lookup can search any searchable field and says what happens when none or several match.

Lookups by search, in the docs

By hand

A value the picklist does not have is one of the reasons Zoho gives for a failed import, and in our test it was kept as typed instead, beside the field's real options. A date column is read in the one format you choose for that field. So the stages and dates are fixed in the spreadsheet first, with helper columns.

In Sloose

Translate values lists every distinct value against the field's real options. Spellings that differ only in capitals, spacing or punctuation are matched for free. For the rest, such as 'Won' against 'Closed Won', the AI can suggest an option, and every option it names is checked against the field before you see it. A value left untranslated stops the run at Validate, so it never reaches your CRM.

By hand

One setting for the whole upload: add as new, update existing, or both, recognised by one unique field. When updating, Zoho can skip empty values, so a blank cell does not clear a field.

In Sloose

A rule per module: accounts by name, contacts by email, or by a formula, such as the email in lower case. When one record matches you choose update or skip. When several match you choose: ask me, use the first, skip, or create. Ask me stops on that row during the run and lets you pick.

By hand

You check the mapping, then import. If the result is wrong, Zoho can undo the records an import added, for 30 days. Updates it made cannot be undone.

In Sloose

Validate checks every module, value and formula before anything is written, and costs nothing. A dry run goes through every row and writes nothing, showing what each row would create or update. Sloose has no undo, so this is where you catch mistakes.

By hand

Zoho offers the list of records with errors for imports in the last seven days. You fix them in the spreadsheet and import that list again, once for each module where something failed.

In Sloose

Failed rows are grouped by the reason your CRM gave. Fix the cause, then Retry runs only the failed rows, and the records that worked are not written again. A retry does not use AI credits, and a retry of a run that ended with failed rows does not count as a new run, up to three in a row. Every run also has a results file: each row, what happened, and the error.

By hand

The splitting, the helper columns and the order of uploads are spreadsheet work, so they are done again with next month's file.

In Sloose

Save the import as a template. Next month, start from it: Sloose checks the new file against it for free, and shows what matched, what was renamed and what is new. Fill the gaps asks the AI only about what the check left open. If nothing is open, there is nothing to pay for.