Switching from ISN
Documentation
There is no ISN-specific importer. Files from Spectora and Home Inspector Pro are recognised by shape; anything else comes in as a spreadsheet, and you map its columns during the import.
That is less of a limitation than it sounds, because the parts of ISN that matter most on a move — contacts and people — are exactly the parts a spreadsheet carries well. The parts it does not carry are the parts no importer would help with either.
What to bring, and how
| From ISN | How |
|---|---|
| Contacts | Export to CSV, import here, map the columns |
| Team members | The same path, as invitations |
| Inspection forms | Rebuilt here — see below |
| Services and fees | Rebuilt by hand; each service can carry its template, agreement, duration and deposit |
| Scheduling rules | Rebuilt in Scheduling, availability and the booking page |
| Past inspections, invoices, signed agreements | Stay where they are |
Forms are the real work
ISN's strength is the office around the inspection — scheduling, agreements, the client interactions. Its form model is not the thing you will be moving line by line, and templates here are structural: sections, items, item types, and canned comments in three tabs.
Two options, and the second is usually right:
- Rebuild the template by hand. Slow, and you get exactly what you want.
- Start from the closest thing you already have. If any of your forms exists as a Spectora-shaped export — inspectors often carry one from an earlier move — import that and edit it here.
Either way, build one template first and run a real inspection on it before converting the rest.
Where the models diverge
- The office is not a separate product here. Scheduling, agreements, invoicing and the client portal are the same system as the report, not an integration around it.
- Agreements are per job, not per document. One envelope covers the order, can carry several signers, and its completion policy decides what "signed" means — Agreements and signatures.
- Your clients get no account. No password, no invitation to accept: a link signs them in to their portal. Anything in your ISN process that assumed a client account can be simplified away.
- Agents get a real account that spans every inspection company naming them, rather than a contact record inside yours.
Running both during a changeover
Same order as any move:
- Build and prove one template.
- Set up services and attach templates to them.
- Take new work here from a chosen date; finish in-flight work where it started.
- Keep ISN readable until your retention obligations for those records are met, and export what you can before closing it.
What to check on day one
- A test booking through your public page, end to end.
- One real inspection, published, delivered to yourself.
- The signing flow, on a phone.
- An invoice, paid with a test card.
That sequence exercises every seam a move actually breaks, and it takes under an hour.
See also: Switching from Spectora.