CRM migration
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
Source
Salesforce Sales Cloud
Destination
Compatibility
10 of 10
objects map 1:1 between LockedOn and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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)
Salesforce Sales Cloud
Contact
1:1LockedOn 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)
Salesforce Sales Cloud
Lead
1:1LockedOn 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
Salesforce Sales Cloud
Account
1:1LockedOn 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
Salesforce Sales Cloud
Custom Property__c object
1:1LockedOn 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)
Salesforce Sales Cloud
Opportunity
1:1LockedOn 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
Salesforce Sales Cloud
Sales Process + Record Type
1:1LockedOn'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)
Salesforce Sales Cloud
Task / Event
1:1LockedOn 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
Salesforce Sales Cloud
Flow (manual rebuild required)
1:1LockedOn 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
Salesforce Sales Cloud
Salesforce Files
1:1LockedOn 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
Salesforce Sales Cloud
Custom Fields on Property__c
1:1LockedOn 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.
| LockedOn | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Contact (client) | Contact1:1 | Fully supported | |
| Contact (lead source) | Lead1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Property | Custom Property__c object1:1 | Fully supported | |
| Deal (active transaction) | Opportunity1:1 | Fully supported | |
| Pipeline | Sales Process + Record Type1:1 | Fully supported | |
| Activity (call, email, meeting) | Task / Event1:1 | Fully supported | |
| Action Plan / Trigger | Flow (manual rebuild required)1:1 | Fully supported | |
| Attachment / File | Salesforce Files1:1 | Fully supported | |
| Custom Property Fields | Custom Fields on Property__c1: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
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
LockedOn
Source
Strengths
Weaknesses
Salesforce Sales Cloud
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 Salesforce Sales Cloud.
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 Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave LockedOn
Other ways to arrive at Salesforce Sales Cloud
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.