CSV and Excel
Workbooks are converted client side, so your file does not have to be reformatted before you start.
Data migration
Bring your existing book in, with your eyes open.
Migration is usually the reason a CRM project stalls. i23 turns it into an upload, a mapping screen, a preview you can trust, and an undo button.
Upload01
Map columns02
Preview03
Confirm04
Undo05
The problem
Moving a book of business is where most CRM rollouts die.
- Exports never match the shape the new system expects
- Imports fail as a whole because of a handful of bad rows
- Duplicates are discovered weeks later, in production
- Nobody can tell what an import actually changed
- There is no way back once the file has been written
The approach
Upload, map, preview, confirm — and undo if you need to.
Spreadsheets are converted in your browser, columns are matched automatically, and every row is validated before anything is written. You see the full outcome first: what will be created, what will be updated, what will be skipped as a duplicate, and which rows cannot be accepted and why.
Suggested mapping
Your column headers are matched to the right fields, and you can correct any suggestion before continuing.
Honest preview
Counts and samples for create, update, skip and reject — produced from the same validation the import itself uses.
Row-level reasons
A rejected row tells you which field failed and why, instead of failing the whole file.
Duplicate detection
Duplicates within the file and against existing records are identified by row before you commit.
Relationship linking
Records are linked to the carriers, companies and contacts they belong to. A required link that cannot be resolved blocks the row; an optional one is noted, not fatal.
Scoped undo
Undo removes only the records a specific import created, leaving everything else untouched.
Import history
Every import is recorded with who ran it, what it touched and the outcome of each row.
Workspace isolated
Imports write only into your own workspace, enforced at the database level.
Workflow
How it moves through the platform
- Upload file
- Map columns
- Validate
- Review preview
- Commit
- Undo if needed
- Go live with your real book, not a sample
- No week of manual re-keying
- Data problems surfaced before they enter the system
- A mistake is reversible in one action
- A record of exactly what was loaded, and by whom