Bringing your old shop across
Connect to Shopmonkey with an API key or bring CSV exports from any system. Both paths preview before writing; their boundaries and undo rules differ.
Owner · Manager · Service advisor · checked 2026-09-14
Moving in from another system
Bringing customers, vehicles, parts and history across — and undoing it.
What is not here
Two different kinds of missing, and they are worth telling apart. One is a feature that does not exist, which no amount of writing would fix. The other is a feature that ships and that we have not documented, which is our backlog and nobody else’s problem to excuse.
- Importing your photosNot built
- Checked again on 2026-09-11. Message history now comes across: matched on the source's own customer identity, linked to a ticket where the source names one, keeping direction, channel and the original time, stamped as imported, and incapable of being sent — the importer takes no transport and maps every row to a state that has already happened. Consent is untouched, and old conversation evidence is not treated as permission for a new message. Bringing conversation history across cannot be undone, because Torqix never deletes a message, and the import screen says so before the shop confirms. PHOTOS still do not come: the source returns signed URLs rather than bytes, there is no vendor-backed allowlist for the host named by that data, and the confirmation snapshot cannot safely keep the capability for later. Those URLs are dropped before anything is stored, and each reference is counted and reported as not fetched. The receipt now tells the shop to download the original arrival photos before ending Shopmonkey access and attach the evidence it needs to keep to the matching repair order in Torqix. Inspections do not come either.