What Sloose does

Sloose takes data you already have — an Excel workbook, a CSV or other delimited text, or rows you paste — and gets it into your CRM as clean, linked records.

Every import starts on Imports, your organisation’s list of them, and is saved as you work: close the tab and it is where you left it. An import goes through five sections, and what worked can be kept as a template to start the next one:

1. Target: the connection it writes to, then the modules you are importing into.
2. Source: paste or upload. Rows can be edited, excluded or filtered by a formula.
3. Map fields: per module, first whether rows are all new, may already exist, or are updates only — and which field recognises an existing record; then each target field takes a column, a fixed value, a formula, or a live search against another module; then picklist values and lookups are translated from what the source says to what the CRM expects. Auto-mapping proposes a starting point, and nothing is applied until you accept it.
4. Validate: type mismatches, over-long values, broken formulas and unmatched references, each with a link back to where it is fixed.
5. Run: dry run first, then the real thing, with a live log that shows each row as it is answered, pause, cancel and retry. Afterwards, the rows with their results are one download away.

Rows can create records in several modules at once and link them. A contact row can create the account it belongs to and point at it, in one pass. The modules are written in your connection’s order, and a link between the row’s records puts the linked module first: a formula that reads another of the row’s records (rec.Account.id), or a lookup that finds one by search on a field the file fills.

Two more things go beyond one record a row. A column of free text can become a note on the record the row makes or updates (Notes on records), and a sheet of line items can be the rows of a subform inside the records it names, replacing what each holds (Rows inside a record).