Import for every Zoho client from one place

Every client's CRM, in one organisation

You connect each client's Zoho CRM with one consent on Zoho's own screen, choosing that client's Zoho organisation. Each is a connection of its own, named for the CRM you chose, with its own modules and fields read from it. How many you can hold depends on the plan:

A client's sandbox counts as a connection like any other. A client who leaves is disconnected, which frees the slot, and the templates and history made through that connection stay. Prices are before tax, billed monthly or yearly with two months free; pricing has the rest. Every plan includes unlimited Sloose users, so your whole team can work in the same organisation.

Every import names the client it writes to

Every import records the connection it writes to, and its Target step shows it. Where there is an obvious one, the CRM of the Zoho tab you opened it from or the organisation's only connection, Sloose pre-selects it and you can change it; with several clients' CRMs and no obvious one, you choose. The run goes to that CRM and no other. A template can remember its client's connection, or name none and have you choose on each import. Writing to the wrong client's CRM is the mistake that cannot be taken back, so the one an import writes to is shown on its Target step, before anything runs.

Deliverables a client can see

• A dry run before anything is written. It goes through every row and rule, searches the client's CRM for existing records as the real run would, and shows for each row whether it would create, update or skip. It writes nothing and does not count as one of the month's runs. How a dry run works.
• A results file for every run that writes. A CSV with every row of the file in order, what the run did with it (written, failed or skipped), the ID of the record it wrote or found in each module, and the CRM's own error where a record was refused. Last month's run can still be downloaded from its history, kept 30 days on Team and 365 on Business and Enterprise. A dry run's file ("would be written") can be downloaded while its panel is on screen; it is not kept in the history, because a dry run wrote nothing.
• A run report you can paste into a ticket. A summary of counts by row and by module, and the step-by-step log behind it.

There is no undo: records a run wrote stay written, which is why the dry run comes first. The results, in the docs.

A client's monthly import, saved once

Save a client's import as a template and start next month's file from it. Sloose checks the new file against what the template expects, finds columns that were renamed or moved, points out new ones, lists values it has not seen, and flags a field the client's CRM has since removed or changed. It cannot see everything in the CRM: a dry run shows what every row would create or update and checks mapping, matching and links, but the CRM's own validation rules and workflows show up only when records are really written. You run it when you are ready; nothing runs by itself. Templates in detail.

Existing records matched, accounts, contacts and deals linked

A client's export is rarely tidy: one sheet with companies, contacts and deals, or three files that refer to each other. Sloose matches rows against the records the client already holds, creates or updates by the rule you choose per module, and links each contact and deal to its account, within one file or across several. You see every row's outcome in the dry run before it is written. Sloose and Zoho CRM.

Far fewer of your client's Zoho API credits

Imports spend the client's Zoho API credits, which is the client's allowance, not yours. Zoho charges one credit per call that writes up to ten records, and a file that only creates new records is sent ten to a call: a hundred new records cost about ten credits, not a hundred. That holds when every module the file creates is set to create everything as new, no field looks up a record the same run creates, and no field is filled after the save. A file that matches existing records, links to records it creates itself, or fills fields after the save is written one record per call, and the searches that find existing records are API calls too. Zoho counts credits over a rolling 24 hours, by edition and licences (Zoho's API limits).