customers.csv1,248 rows
CustomersAll fields mapped
ReadyMove into Nesto
Bring the data. Keep the structure and meaning.
Export from the CRM or spreadsheets you use today. Nesto gives you a visible plan, a dry review, exact totals, and a safe way back before the migration is accepted.
New migrationReview before import
SourceCRM export4 CSV files · 8,532 rows
DestinationOld Cap workspace4 modules · 42 fields
properties.csv986 rows
PropertiesAll fields mapped
Readyjobs.csv3,422 rows
Jobs12 mapped fields
Check 3invoices.csv2,876 rows
InvoicesAll fields mapped
ReadyCSV is the canonical staged format. CSV, XLSX, and bounded CRM export ZIP files normalize locally into that path. Attachments, owners, activities, and direct connectors are not imported yet.
Five clear stages. No mystery button.
Every stage answers a different question: what is here, where should it go, what needs attention, what changed, and did the result match the plan?
01
Discover
Nesto reads file structure, headers, row counts, and likely relationships before it proposes a destination.
02
Map
Match source files and columns to modules, fields, options, and linked records.
03
Check
Review warnings, duplicates, invalid values, and unresolved relationships before a record is written.
04
Import
Apply the exact reviewed plan with stable source identifiers, progress totals, and safe retries.
05
Reconcile
See what was created, updated, skipped, or rejected, then keep the batch or conservatively roll back untouched records it created.
Relationships matter
A contact list is easy. Rebuilding the story is the real work.
Nesto maps shared source identifiers, emails, phone numbers, and names so jobs, properties, invoices, and other records can reconnect to the right parent record.
Uncertain links stay visible for review. Nesto does not silently attach a child record to the first name that looks close.
contacts.csvExternal ID: C-1042
jobs.csvCustomer ID: C-1042
invoices.csvJob ID: J-8801
AI, when you choose it
Let AI suggest. Let deterministic checks decide.
Smart Import can send normalized source names, headers, and a bounded sample of rows to the configured AI provider to propose a mapping. It never turns that proposal directly into records.
- You can use manual mapping instead
- The exact disclosure appears before analysis
- Every proposed field and relationship is validated
- The final apply step uses the reviewed plan, not a new AI response
Import safety
Designed so retrying is boring.
Network interruptions and large files should not turn into duplicate customers or a migration nobody can explain.
Plan binding
The applied import must match the exact files and plan that were previewed.
Idempotent retry
Repeating the same request cannot quietly create a second copy.
Workspace isolation
Every batch, record, event, and permission check stays inside its workspace.
Bounded payloads
File size, row count, field count, and value length have explicit limits.
Conservative rollback
Nesto removes records created by the batch only when nothing else has taken ownership of them.
Completion report
Every row gets an outcome.
The completion view separates created, updated, skipped, and rejected source rows. The downloadable report keeps opaque source keys, fingerprints, stable reason codes, and destination record IDs without copying raw source cells into the audit ledger.
Safe to retryThe same batch continues from durable state.
Rollback availableUntouched created records can be removed without deleting later edits or activity.
ModuleRowsCreatedUpdatedIssues
Customers1,2481,232115
Properties98698600
Jobs3,4223,401165
Invoices2,8762,87042
8,532 rows reconciled29 items need review before acceptance
A careful way home
Your next CRM should know where every record came from.
Move in with a visible plan, understandable totals, and a migration history you can inspect after the work is done.
Build your workspace