CRM migration
Field-level mapping, validation, and rollback between LockedOn and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
LockedOn
Source
Freshsales
Destination
Compatibility
9 of 10
objects map 1:1 between LockedOn and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
LockedOn structures its CRM around real estate workflows: contacts are associated with properties, vendors are tracked separately, and deals are tied to listings rather than standard opportunity pipelines. Freshsales uses the conventional lead-contact-account-deal model with lifecycle stages, deal stages, and sales activities. We map LockedOn contacts to Freshsales Contacts and Accounts, LockedOn properties to Freshsales Deals with custom fields for listing details, and LockedOn vendors to Freshsales Accounts. LockedOn's triggers (automated follow-up on OFI attendance, post-enquiry sequences) have no equivalent in Freshsales and must be rebuilt using Freshsales' Workflows and Sales Sequences. Activity history — emails, calls, meetings logged in LockedOn — migrates as Freshsales Sales Activities. Our migration uses scoped read access to LockedOn's API, extracts all standard and custom fields, and loads into Freshsales via the Freshsales API with owner resolution by email match. A delta-pickup window captures any records modified during cutover before you go live on Freshsales.
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 Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
LockedOn
Contact
Freshsales
Contact
1:1LockedOn contacts migrate directly to Freshsales Contacts. Each contact retains first name, last name, email, phone, job title, address, and any custom properties. The contact's primary property association in LockedOn becomes a Deal link in Freshsales tied to the contact via a Contact Role.
LockedOn
Contact
Freshsales
Lead
1:manyLockedOn contacts that have not yet been converted to active clients route to Freshsales Leads if your team uses lead-conversion workflows. Decision rule: contacts with status 'enquiry' or 'prospect' without a closed deal map to Lead; contacts with at least one active deal map to Contact.
LockedOn
Property
Freshsales
Deal
1:1LockedOn's Property object has no direct Freshsales equivalent. We map it to a Freshsales Deal where Deal.Name = Property address, Deal.Amount = listing price, and Deal stage reflects property status (Active Listing, Under Contract, Sold). Property-specific fields (bedrooms, bathrooms, property_type, listing_agent) migrate as custom fields on the Deal.
LockedOn
Vendor
Freshsales
Account
1:1LockedOn vendors (landlords, property managers, service providers) map to Freshsales Accounts. Vendor-specific fields like vendor_type, commission_rate, and property_portfolio migrate as custom Account fields. Each vendor's linked properties in LockedOn become Deals in Freshsales associated with the vendor Account via a direct relationship that your team can review and confirm before migration.
LockedOn
Enquiry
Freshsales
Lead
1:1LockedOn enquiries (inbound property inquiries, OFI sign-ups) map to Freshsales Leads with lifecycle stage set to 'Lead'. Enquiry source, enquiry_date, and property_reference migrate as custom Lead fields. If the enquiry converts to a contact in LockedOn, the corresponding Freshsales record updates to Contact status.
LockedOn
Task / Plan
Freshsales
Task
1:1LockedOn task plans (automated follow-up sequences, OFI attendance tasks) migrate as Freshsales Tasks with the original task name, due date, and owner. Note: the automated trigger logic behind the task plan does not migrate — it must be rebuilt as a Freshsales Workflow or Sales Sequence.
LockedOn
Activity (Call, Email, Meeting)
Freshsales
Sales Activity
1:1LockedOn engagement records — calls logged, emails sent, meetings held — migrate as Freshsales Sales Activities. Original timestamps, activity type, and owner are preserved. Activity is linked to the parent contact or deal record based on LockedOn's original association model, and your team can verify linkage accuracy during the reconciliation phase after migration.
LockedOn
Attachment / File
Freshsales
File
1:1LockedOn files attached to contacts, properties, or vendors (floor plans, contracts, marketing PDFs) re-upload to Freshsales Files and attach to the corresponding record. File size limits (Freshsales caps at 25MB per file) are enforced during migration; larger files are flagged for manual handling.
LockedOn
Custom Property Fields
Freshsales
Custom Field
1:1LockedOn custom properties on contacts, properties, vendors, and enquiries (e.g., lead_source_detail, vendor_commission_tier, property_council_area) migrate as Freshsales custom fields. Field type is preserved: text stays text, pick-list stays pick-list, number stays number. Pick-list values are mapped individually, and we verify each mapping during the planning phase before migration runs.
LockedOn
Tag
Freshsales
Tag
1:1LockedOn tags applied to contacts, properties, and vendors migrate as Freshsales Tags. Tags are preserved at the record level and can be used for segmentation and filtering in Freshsales without any transformation. We validate tag count matches between source and destination during reconciliation to confirm complete transfer.
| LockedOn | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Contact | Lead1:many | Fully supported | |
| Property | Deal1:1 | Fully supported | |
| Vendor | Account1:1 | Fully supported | |
| Enquiry | Lead1:1 | Fully supported | |
| Task / Plan | Task1:1 | Fully supported | |
| Activity (Call, Email, Meeting) | Sales Activity1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported | |
| Custom Property Fields | Custom Field1:1 | Fully supported | |
| Tag | Tag1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Extract LockedOn data via scoped read access
We connect to LockedOn using scoped read-only API credentials you provision in your LockedOn account settings. We extract all contacts, vendors, properties, enquiries, tasks, activities, and files — plus every custom property defined on each object. The export is staged in our secure migration environment with encryption at rest. We validate record counts against your LockedOn data and flag any objects that are empty or require special handling (e.g., locked records, records with missing email addresses). This extraction step establishes the baseline dataset for the entire migration.
Map object model and create Freshsales custom fields
We build the object mapping plan (Contact, Lead, Account, Deal, Task, Sales Activity) and identify all custom fields needed on each Freshsales object based on the custom properties found in the LockedOn extraction. If your Freshsales instance already has matching custom fields, we use those identifiers. If not, we create them programmatically using the Freshsales API before the migration run begins. We deliver the complete field map as a review artifact — you approve it before any data movement starts.
Resolve owners by email match and stage the migration order
LockedOn owner IDs are resolved against Freshsales users by email address lookup. Unmatched owners are flagged in a pre-flight report — your team either invites them to Freshsales first or designates a fallback owner. We sequence the migration in dependency order: Accounts and Contacts load first because other records reference them as foreign keys; then Deals are created and linked to the corresponding vendor Account; then Activities and Tasks are attached to the correct parent contact or deal records.
Run a sample migration with field-level diff
Before committing to the full migration, we run a representative sample of 100–300 records that covers a cross-section of contacts, properties, vendors, and activity types. We generate a field-level diff comparing source values against destination values, so you can verify that the mapping logic produced the expected results. You review the sample, confirm the data looks correct, and provide sign-off before we schedule the full migration run.
Execute full migration with delta-pickup window
The full migration runs against your Freshsales instance via the Freshsales REST API. During cutover, your team continues working in LockedOn without interruption. A 24–48 hour delta-pickup window captures any records created or modified after the initial extraction was taken. Once delta is applied, we run reconciliation: record counts, field-level validation, and activity linkage verification. One-click rollback is available if reconciliation reveals unexpected issues.
Platform deep dives
LockedOn
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Freshsales.
Object compatibility
2 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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your LockedOn to Freshsales 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 Freshsales
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.