CRM migration
Field-level mapping, validation, and rollback between LockedOn and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
LockedOn
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between LockedOn and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
LockedOn structures its CRM around real estate-specific objects: People linked to Companies, Deals tied to specific Properties, and automation triggers for open homes, OFI follow-ups, and vendor reporting. Nutshell uses a standard small-business CRM model — People, Companies, Leads, and Deals — with no native property object. This mismatch is the core challenge of the migration: real estate context that lives in LockedOn's property associations has no direct landing pad in Nutshell. FlitStack AI solves this by mapping People to Nutshell People, Companies to Nutshell Companies, and Deal-to-Property associations to custom fields on both the Deal and the associated Company record, so property addresses, listing statuses, and vendor relationships survive the transition. Standard fields (name, email, phone, stage, amount, close date) map directly. LockedOn's automation triggers — OFI follow-up rules, welcome sequences, post-enquiry workflows — do not migrate and must be rebuilt in Nutshell's automation engine after cutover. We execute the migration via read-only API access to LockedOn, with data validated against a field-level diff before the full run commits.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a LockedOn object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
LockedOn
Person
Nutshell
Person
1:1LockedOn People map directly to Nutshell People. Name, email, phone, and address fields migrate as-is. A LockedOn Person's type (agent, vendor, landlord, buyer) is stored in a custom pick-list field when the value set does not match Nutshell's default options. If any required Nutshell fields are missing in the source, they are flagged during the test migration for immediate correction before the full run.
LockedOn
Company
Nutshell
Company
1:1LockedOn Company records map to Nutshell Companies. Agency name, website, and industry map directly. LockedOn's parent/branch company hierarchy migrates to Nutshell's parent company field. Multi-company contacts collapse to a primary Company link; secondary links are noted in a custom field for post-migration review.
LockedOn
Lead
Nutshell
Lead
1:1LockedOn Leads map directly to Nutshell Leads, preserving status and source through value‑by‑value lookup. Any status values not present in Nutshell are added as custom options to maintain continuity. Custom lead fields such as enquiry source, budget range, or property interest are created as Nutshell custom fields prior to migration. All custom fields are validated for data type consistency during the test phase.
LockedOn
Deal
Nutshell
Deal
1:1LockedOn Deals map to Nutshell Deals with pipeline stages mapped to Nutshell pipeline stages. Each LockedOn deal pipeline maps to one Nutshell pipeline. Stage names use value-mapping to preserve the same ordering and naming convention your team recognizes. If a LockedOn pipeline has no direct Nutshell counterpart, a new Nutshell pipeline is created with matching stage structure. Custom stage fields are carried over as custom fields on the Deal record.
LockedOn
Property
Nutshell
Deal + Company (custom fields)
1:1LockedOn Property records have no Nutshell equivalent. We flatten property data into custom fields on the associated Deal record (listing address, property type, price guide, inspection dates) and on the Company record (if the company is a landlord or vendor). This preserves all property context without creating orphan records.
LockedOn
Vendor
Nutshell
Company (custom fields)
1:1LockedOn Vendor records map to Nutshell Companies with a Vendor_Type__c custom pick-list field set to 'Vendor'. Vendor portal URL and reporting preferences land in custom text fields. Vendor contact persons map as Nutshell People linked to the vendor Company record.
LockedOn
Activity / Bulk Communication
Nutshell
Task + Activity
1:1LockedOn activity history (calls, emails, meeting notes) migrates as Nutshell Tasks and Activities with original timestamps and assigned owners preserved. Bulk agency communications that were one-to-many in LockedOn split into individual Activity records, one per recipient. Attachments associated with activities are stored as links in the activity description, and any activity categories are mapped to Nutshell task types to maintain categorization.
LockedOn
Note
Nutshell
Note
1:1LockedOn notes migrate as Nutshell Notes, linked to the parent record (Person, Company, or Deal). Rich-text formatting is preserved. Notes on property inspections carry the inspection address in the note body for searchability in Nutshell. If a note references a related property or contact, the reference is preserved as a clickable link to the migrated record. Any embedded images are migrated as attachments to maintain full context.
LockedOn
QR Check-in Record
Nutshell
Activity (linked to Deal)
1:1LockedOn's QR check-in records for open-for-inspection events have no Nutshell equivalent. Each attendee check-in migrates as a Task record linked to the associated Deal (representing the inspection), with the attendee's name and contact in the task description. Original check-in timestamps are preserved.
LockedOn
Custom Field (real estate property)
Nutshell
Custom Field (Deal or Company)
1:1Every unique property-level custom field in LockedOn — listing status, council rates, zoning, days on market, auction date — requires a corresponding custom field in Nutshell created before data lands. We audit LockedOn's full custom field list during discovery and deliver a Nutshell field-creation plan as part of the migration pack.
| LockedOn | Nutshell | Compatibility | |
|---|---|---|---|
| Person | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Property | Deal + Company (custom fields)1:1 | Fully supported | |
| Vendor | Company (custom fields)1:1 | Fully supported | |
| Activity / Bulk Communication | Task + Activity1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| QR Check-in Record | Activity (linked to Deal)1:1 | Fully supported | |
| Custom Field (real estate property) | Custom Field (Deal or Company)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
LockedOn gotchas
No public API documented for customer use
Automations are not exportable
Vendor Portal records are platform-locked
QR check-in data not independently exportable
Custom fields may require reconfiguration post-migration
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and LockedOn data audit
FlitStack AI connects via read-only API access to your LockedOn instance to inventory all object types, field definitions, custom property sets, and deal-to-property associations. We identify every unique property field (listing status, price guide, zoning, inspection schedule, auction date) and every vendor relationship that requires a custom field in Nutshell. We also audit your automation triggers and bulk communication templates to produce the reference document you will use to rebuild them in Nutshell. This phase produces the migration specification: a field-by-field map plus a Nutshell custom-field creation plan.
Build Nutshell custom fields and pipelines
Before data moves, your Nutshell admin (or our team) creates the custom fields identified during discovery. Property address, price guide, property type, auction date, vendor type, and portal URL all require custom fields on the Deal or Company object. We deliver a step-by-step field creation plan mapped to each LockedOn source field so nothing is missed. If your LockedOn instance uses multiple deal pipelines, we also create matching Nutshell pipelines and stage sets so stage mapping resolves cleanly during the migration run.
Resolve owners and test migration
LockedOn owner email addresses are matched against Nutshell user accounts. Any LockedOn owner with no matching Nutshell user is flagged before migration — your team either creates the Nutshell user account first or assigns those records to a fallback owner. We run a test migration of a representative sample (typically 100–300 records spanning contacts, companies, deals, and activities) and generate a field-level diff so you can verify that property fields landed correctly, vendor associations are intact, and owner resolution worked across the sample before the full run proceeds.
Full migration with delta-pickup cutover
The full migration runs against Nutshell's JSON-RPC API. All People, Companies, Leads, Deals, Activities, Notes, and custom field data loads in dependency order: Companies first (to receive foreign keys), then People linked to Companies, then Deals linked to People and property fields, then Activities and Notes. A delta-pickup window of 24–48 hours after the full run captures any records created or modified in LockedOn during the cutover window. An audit log records every operation. One-click rollback is available if reconciliation against your LockedOn record counts shows a discrepancy exceeding the agreed threshold.
Post-migration reconciliation and rebuild handoff
We deliver a reconciliation report comparing LockedOn and Nutshell record counts by object type, with a field sampling verification showing mapped values against source. Any records that fell out (due to invalid email formats, missing required fields, or API errors) are listed with the root cause. We hand off the automation rebuild reference document so your Nutshell admin can configure triggers, post-enquiry sequences, and OFI follow-up workflows using Nutshell's automation engine. Any QR check-in historical data exported before cutover is handed back as a structured CSV for long-term reporting outside Nutshell.
Platform deep dives
LockedOn
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across LockedOn and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
LockedOn: Not publicly documented.
Data volume sensitivity
LockedOn doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during LockedOn to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your LockedOn to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave LockedOn
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.