CRM migration

Migrate from LockedOn to Nutshell

Field-level mapping, validation, and rollback between LockedOn and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

LockedOn logo

LockedOn

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between LockedOn and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

LockedOn logo

LockedOn

What's pushing teams away

  • Limited public API documentation makes LockeOn difficult to integrate with external tools, prompting agencies with custom tech stacks to seek alternatives.
  • Opaque pricing not published on the website causes uncertainty and forces sales conversations before evaluation.
  • Small team size (11 employees per LinkedIn) raises concerns about long-term platform stability and feature development pace.
  • Agents report that the automation builder, while powerful, lacks flexibility for complex conditional workflows beyond standard triggers.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How LockedOn objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Company

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Lead

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Deal

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Deal + Company (custom fields)

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Company (custom fields)

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Task + Activity

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Note

1:1
Fully supported

LockedOn 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

maps to

Nutshell

Activity (linked to Deal)

1:1
Fully supported

LockedOn'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)

maps to

Nutshell

Custom Field (Deal or Company)

1:1
Fully supported

Every 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.

Gotchas + challenges

What specifically takes care here

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 logo

LockedOn gotchas

High

No public API documented for customer use

High

Automations are not exportable

Medium

Vendor Portal records are platform-locked

Medium

QR check-in data not independently exportable

Low

Custom fields may require reconfiguration post-migration

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Property associations require custom fields since Nutshell has no native property object

    LockedOn treats Property as a first-class object that Deals reference, with fields for listing address, price guide, property type, inspection schedule, and auction date. Nutshell has no property object and no deal-property association model. We flatten property data into custom fields on the Deal record and on the associated Company record for landlord and vendor contexts. The limitation is that Nutshell's pipeline views show only standard deal fields by default — property context is visible by opening the record, not in the pipeline card. Teams that rely on property-at-a-glance pipeline views should plan Nutshell's custom pipeline layout configuration after migration.

  • LockedOn automation triggers (OFI follow-up, post-enquiry, anniversary tasks) do not migrate

    LockedOn's trigger system automates hours of work per week by completing tasks based on CRM events — open-home attendance triggers OFI follow-up, post-enquiry sequences fire welcome emails, and anniversary tasks remind agents of client milestones. Nutshell's automation engine (available in Pro and above) operates on a different model: sequences start when a lead enters a pipeline stage and run per-contact. Cross-object event chains from LockedOn cannot be replicated automatically. FlitStack AI migrates data only. We export your LockedOn trigger definitions as a written reference document your team can use to configure Nutshell automations manually or with a Nutshell consultant. This must be scoped separately from the data migration.

  • Vendor reporting portal data migrates as fields with no live portal equivalent

    LockedOn's 24/7 Vendor Portal gives sellers automatic visibility into their listing's marketing activity, open-home attendance, and enquiry volume. Nutshell has no vendor portal feature. We migrate the portal URL and any vendor-specific reporting fields as read-only custom fields on the Company record, but the live portal experience is not reproduced. Vendors who currently self-serve through the LockedOn portal will need an alternative process after cutover — typically a weekly summary email sent manually or via Nutshell's email sequences.

  • Multi-company contacts collapse to a single primary Company link in Nutshell

    LockedOn supports many-to-many contact-to-company associations natively — a buyer agent can be linked to multiple agency companies simultaneously. Nutshell links each Person to one primary Company, with secondary associations requiring manual linking in the UI after migration. We migrate the most recently modified company association as primary and preserve other company IDs in a Source_System_Refs__c custom field for manual re-linkage. This is a post-migration data stewardship task, not a data-loss condition, but it requires admin attention for high-value contacts with complex company affiliations.

  • LockedOn's QR check-in data migrates as tasks with limited searchability

    LockedOn's QR Check-in feature captures attendee registration and feedback at open-for-inspection events, associating check-in records with a specific property and timestamp. Nutshell has no event-registration or open-home tracking construct. Each check-in migrates as a Task record linked to the associated Deal, with the attendee's name and contact in the task description. The original check-in timestamp is preserved. However, Nutshell's search and reporting tools do not aggregate check-in data across inspections the way LockedOn's reporting does — teams should export historical QR data separately before cutover for any reporting that requires cross-inspection analysis.

Migration approach

Six steps for a successful LockedOn to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

LockedOn logo

LockedOn

Source

Strengths

  • Integrated CRM, marketing automation, and vendor reporting in a single real estate-focused platform.
  • Pre-built automation templates for OFI follow-up and post-enquiry welcome sequences.
  • QR check-in for contactless open home registrations.
  • Vendor portal with 24/7 reporting access for sellers.
  • Bulk communication engine with templating for routine client outreach.

Weaknesses

  • No publicly documented REST API accessible to customers for data export or integration.
  • Opaque pricing model requiring direct sales contact to obtain quotes.
  • Small development team limits pace of feature updates and support capacity.
  • Automation rebuild is manual on destination platforms since automations cannot be exported.
  • Limited object model means complex agency workflows may require custom workarounds.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across LockedOn and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    LockedOn: Not publicly documented.

  • Data volume sensitivity

    B

    LockedOn doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your LockedOn to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about LockedOn to Nutshell data migrations

Answers to the questions buyers ask most during LockedOn to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your LockedOn to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most LockedOn-to-Nutshell migrations complete within 48–72 hours of clock time for setups under 25,000 records. Larger databases with extensive custom property fields (listing status, auction date, inspection schedules) or complex deal-to-property associations extend the timeline to 5–8 days. The longest planning step is building the Nutshell custom field schema before the migration run, not the data transfer itself. A test migration of a representative sample (100–300 records) validates field mapping and flags missing required values before the full run. After the primary load, a delta‑pickup window of 24–48 hours captures any new or updated LockedOn records, ensuring Nutshell reflects the latest data at cutover.

Adjacent paths

Related migrations to explore

Ready when you are

Move from LockedOn.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day