CRM migration

Migrate from LockedOn to Salesforce Sales Cloud

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

LockedOn logo

LockedOn

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

100%

10 of 10

objects map 1:1 between LockedOn and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

LockedOn is a property-centric CRM built for real estate agencies, with clients, properties, and deals tied together through an automation engine of triggers and action plans. Salesforce Sales Cloud operates on a fundamentally different data model: Accounts and Contacts are separate objects with a lookup relationship, Opportunities track revenue-generating deals with StageName pick-lists and RecordTypeId scoping, and all automation lives in Flow rather than rule-based triggers. We extract your LockedOn data via API (contacts, companies, properties, active deals, activities with timestamps and owners) and load it into Salesforce using Bulk API for high-volume records and REST API for precision mapping. Properties that don't fit Opportunity's standard schema land as a custom Property__c object with status, price, and type fields. Workflows, triggers, and action plans do not migrate — we deliver a structured export of your LockedOn automation logic as a rebuild reference for your Salesforce admin or consultant. Owner resolution runs by email match against Salesforce users before records commit, and a 48-hour delta window captures any changes made in LockedOn during cutover.

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

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How LockedOn objects map to Salesforce Sales Cloud

Each row shows how a LockedOn object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

LockedOn

Contact (client)

maps to

Salesforce Sales Cloud

Contact

1:1
Fully supported

LockedOn contact records map directly to Salesforce Contact. The primary challenge is that LockedOn embeds property associations directly on the contact, while Salesforce requires an AccountId lookup to an Account record. We resolve this by migrating the most-recently-linked property as the primary AccountId and surfacing additional property associations as related Opportunity records.

LockedOn

Contact (lead source)

maps to

Salesforce Sales Cloud

Lead

1:1
Fully supported

LockedOn contacts that originated as enquiries (unsold leads) route to Salesforce Lead. The distinction between Contact and Lead in Salesforce mirrors LockedOn's distinction between 'Client' (active relationship) and 'Lead' (initial enquiry). FlitStack uses the contact's deal status in LockedOn to determine the correct Salesforce object.

LockedOn

Company

maps to

Salesforce Sales Cloud

Account

1:1
Fully supported

LockedOn company records (vendor names, property owner entities) map 1:1 to Salesforce Account. Parent-company hierarchies in LockedOn translate to Account.ParentId in Salesforce. Multi-company associations on a single contact collapse to one primary AccountId with Account Contact Relations for the rest.

LockedOn

Property

maps to

Salesforce Sales Cloud

Custom Property__c object

1:1
Fully supported

LockedOn property records have no Salesforce standard equivalent — Opportunity tracks a deal, not a physical property listing. We create a Property__c custom object with fields for listing price (Decimal), property type (picklist), inspection dates (Date), listing status (picklist), and vendor feedback (Long Text Area). Property__c links to the primary Account (owner/vendor) and to related Opportunity records for active transactions.

LockedOn

Deal (active transaction)

maps to

Salesforce Sales Cloud

Opportunity

1:1
Fully supported

LockedOn deals with status 'Under Contract', 'Settlement', or 'Sold' map to Salesforce Opportunity. The LockedOn pipeline stage (Potential, Listed, Under Contract, Sold) maps to Salesforce Opportunity StageName values, which must be configured per Record Type before migration. Stage-entered timestamps are preserved as custom datetime fields on the Opportunity.

LockedOn

Pipeline

maps to

Salesforce Sales Cloud

Sales Process + Record Type

1:1
Fully supported

LockedOn's single or multi-pipeline configuration maps to Salesforce Sales Processes keyed by Record Type. Each LockedOn pipeline requires its own Salesforce Record Type (e.g., Residential_Sales, Commercial_Leasing) so that stage pick-list values and page layouts vary by deal type. FlitStack delivers a record-type setup plan as part of the migration package.

LockedOn

Activity (call, email, meeting)

maps to

Salesforce Sales Cloud

Task / Event

1:1
Fully supported

LockedOn activity records (calls, emails, meetings logged against contacts or properties) map to Salesforce Task (for calls and emails) and Event (for meetings). Original timestamps, owners, and the WhatId or WhoId parent link are preserved. Vendor feedback notes from LockedOn's property inspection workflow migrate as Task records with Type='Vendor Feedback'.

LockedOn

Action Plan / Trigger

maps to

Salesforce Sales Cloud

Flow (manual rebuild required)

1:1
Fully supported

LockedOn action plans (automated task sequences triggered by CRM events) and triggers do not have a Salesforce equivalent that auto-migrates. FlitStack exports a structured JSON + Markdown reference document listing every trigger, its firing condition, and the resulting action sequence so your Salesforce admin can rebuild equivalents in Flow Builder.

LockedOn

Attachment / File

maps to

Salesforce Sales Cloud

Salesforce Files

1:1
Fully supported

LockedOn file attachments (contracts, inspection reports, listing photos) are downloaded and re-uploaded to Salesforce Files, linked to the corresponding Property__c or Opportunity record. Salesforce's 25MB per-file limit applies; files exceeding this are flagged for chunked upload or alternative storage reference.

LockedOn

Custom Property Fields

maps to

Salesforce Sales Cloud

Custom Fields on Property__c

1:1
Fully supported

LockedOn custom fields on property records (e.g., 'Council Rates', 'Rental Yield', 'Auction Date') migrate as custom fields on the Property__c object. Field type mapping: text → Text(255), numbers → Number, pick-lists → Picklist with value-by-value mapping. The __c suffix is applied per Salesforce naming convention.

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

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • Property-to-Opportunity split requires a custom object that must be pre-created in Salesforce

    LockedOn conflates property listings and sales transactions in one deal record. Salesforce separates these into a Property__c custom object (listing metadata) and an Opportunity (the revenue transaction). If your Salesforce admin has not pre-created Property__c with the necessary custom fields before migration, records that should land as Property__c will fail validation and pause the migration run. FlitStack delivers the full field specification for Property__c as part of the pre-migration schema plan so your org is ready before data moves.

  • LockedOn triggers and action plans have no auto-migration path to Salesforce Flow

    LockedOn's trigger engine fires automated task sequences when CRM events occur (e.g., 'When enquiry created, create follow-up task and send SMS'). Salesforce Flow is the functional equivalent but requires manual rebuild — there is no automated conversion tool that preserves LockedOn's conditional logic inside Salesforce's flow XML structure. FlitStack exports your trigger definitions as a structured JSON document and Markdown step-list so your Salesforce admin can recreate the logic in Flow Builder without reverse-engineering the source system.

  • QR check-in and vendor portal data cannot be replicated as native Salesforce objects

    LockedOn's QR check-in platform and 24/7 vendor portal are proprietary features that store attendee registration data and vendor-facing status updates. Salesforce has no native vendor portal or event check-in object. The check-in count migrates as a number field on Property__c (QR_Check_In_Count__c), but the full attendee list and portal activity history cannot be represented in Salesforce without a custom Experience Cloud build. We flag these as reference-only data and note them in the migration plan.

  • LockedOn pipeline stages require value-by-value mapping per Salesforce Record Type

    LockedOn's deal pipeline stages (Potential, Listed, Under Contract, Sold) are a single flat pick-list. Salesforce scopes StageName values inside a Record Type, meaning 'Listed' as a stage on a Residential record type is a different pick-list entry from 'Listed' on a Commercial record type. Teams running multiple property types in LockedOn end up with multiple Salesforce Record Types, each needing its own stage configuration. We generate a stage-mapping matrix per record type before migration so your admin can pre-configure the correct pick-list values.

  • LockedOn's per-agency licensing means user-seat mapping is 1:1 or N:1 rather than a direct import

    LockedOn charges per agency with shared access, while Salesforce charges per named user with individual licenses. If your LockedOn account has 15 agents sharing access under one login, those 15 agents need 15 Salesforce licenses after migration. FlitStack matches LockedOn owner IDs to Salesforce users by email — but your team must confirm which users require Salesforce licenses before owner resolution runs, as unassigned records fall to a fallback owner rather than a named user.

Migration approach

Six steps for a successful LockedOn to Salesforce Sales Cloud data migration

  1. Audit LockedOn data model and extract via API

    FlitStack connects to LockedOn via API using scoped read access and exports all standard objects (contacts, companies, properties, deals, activities) along with any custom fields in use. We produce a data inventory showing record counts per object, custom field inventory, and a sample of pipeline stage values and trigger definitions. This inventory drives the Salesforce schema plan and field-mapping spreadsheet.

  2. Deliver Salesforce schema setup plan and field-mapping spreadsheet

    Based on the LockedOn inventory, FlitStack produces a Salesforce-specific setup plan: custom Property__c object with field specifications, record type names per pipeline, stage value matrices per record type, and a field-mapping spreadsheet where each LockedOn field has a Salesforce destination. Your Salesforce admin (or our team) creates the schema before data lands. Automation export document is delivered alongside the schema plan.

  3. Resolve owners by email match and flag unmapped users

    LockedOn owner IDs are matched against Salesforce users by email address. Any owner in LockedOn that has no corresponding Salesforce user is flagged with a fallback owner recommendation before migration runs. No record commits without a valid OwnerId. We surface unmatched owners in a pre-flight report so your team can invite them to Salesforce or assign a designated fallback owner before the migration begins.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records (spanning contacts, accounts, properties, opportunities, and activities) migrates first using Bulk API for high-volume objects and REST API for precision-mapped records. FlitStack generates a field-level diff report comparing source values to destination values so you can verify pipeline-to-record-type mapping, property__c field population, owner resolution, and activity linking before the full run commits. This validation step also checks date preservation, custom field data integrity, and the correct application of picklist value mappings across record types.

  5. Execute full migration with delta-pickup window

    The full dataset migrates to Salesforce. During the cutover window (typically 24–48 hours after the initial run completes), a delta-pickup phase captures any records created or modified in LockedOn while the initial migration was running. FlitStack's audit log records every insert, update, and link operation. If reconciliation fails or record counts are outside tolerance, one-click rollback reverts the Salesforce org to its pre-migration state for a clean retry.

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.
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

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 Salesforce Sales Cloud.

  • 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 Salesforce Sales Cloud 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 Salesforce Sales Cloud data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most LockedOn-to-Salesforce migrations complete in 48–72 hours of clock time for under 50,000 records. Larger setups with 500,000+ records or heavy custom-object usage (particularly Property__c with dozens of custom fields) extend to 7–14 days. The longest planning step is creating the Salesforce record types, Property__c object, and stage value matrices before data can validate and commit. During this window FlitStack performs a pre-flight validation of field mapping, runs the initial bulk load, and then captures any final changes via a delta-pickup pass. If your org has multiple record types or complex validation rules, the planning and setup of those elements typically adds one to two days to the overall schedule.

Adjacent paths

Related migrations to explore

Ready when you are

Move from LockedOn.
Land in Salesforce Sales Cloud, 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