CRM migration

Migrate from LockedOn to Freshsales

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

LockedOn logo

LockedOn

Source

Freshsales

Destination

Freshsales logo

Compatibility

90%

9 of 10

objects map 1:1 between LockedOn and Freshsales.

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

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How LockedOn objects map to Freshsales

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

maps to

Freshsales

Contact

1:1
Fully supported

LockedOn 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

maps to

Freshsales

Lead

1:many
Fully supported

LockedOn 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

maps to

Freshsales

Deal

1:1
Fully supported

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

maps to

Freshsales

Account

1:1
Fully supported

LockedOn 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

maps to

Freshsales

Lead

1:1
Fully supported

LockedOn 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

maps to

Freshsales

Task

1:1
Fully supported

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

maps to

Freshsales

Sales Activity

1:1
Fully supported

LockedOn 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

maps to

Freshsales

File

1:1
Fully supported

LockedOn 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

maps to

Freshsales

Custom Field

1:1
Fully supported

LockedOn 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

maps to

Freshsales

Tag

1:1
Fully supported

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

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Property-to-Deal mapping requires custom field setup before data lands

    LockedOn's Property object has no native equivalent in Freshsales. Every property migrates as a Deal with address as Deal.Name and listing price as Amount, but listing-specific fields (bedrooms, bathrooms, property_type, council_area) need Freshsales custom fields created on the Deal object before migration runs. If these fields don't exist, the migration engine flags them and either creates them automatically or pauses for admin approval — either way, your schema plan is the critical path item for this migration pair.

  • LockedOn triggers and automation plans don't transfer to Freshsales Workflows

    LockedOn's Triggers automate follow-up actions based on events (OFI attendance, post-enquiry welcome, anniversary reminders). Freshsales Workflows are condition-action rules that fire on record changes — the logic model is fundamentally different and there is no automated conversion path. We export your trigger definitions as a text reference document so your Freshsales admin can rebuild them manually. This is disclosed honestly: automation rebuild is a separate workstream that FlitStack can scope on request.

  • Vendor object maps to Account but loses the property-link graph

    LockedOn vendors are linked to properties through a native association object. Freshsales has no equivalent many-to-many vendor-property relationship — each vendor is an Account and each property is a Deal, but the link between them requires a custom junction or manual linking. We surface this during migration planning: you choose whether to link every Deal to its vendor Account at migration time or accept the links as a post-migration cleanup task.

  • Freshsales contact lifecycle stages need value mapping from LockedOn status

    LockedOn tracks contact engagement status but lacks lifecycle stage equivalents that Freshsales requires. Freshsales' Contact Lifecycle Stage field uses defined values: Subscriber, Lead, MQL, SQL, Opportunity, and Customer. We map your LockedOn status values to the closest matching Freshsales lifecycle stage, but your team should review the mapping configuration before migration runs. Misaligned lifecycle stages can affect lead routing, automation triggers, and reporting in Freshsales if contacts land in incorrect stages for your sales process workflow.

  • File attachments over 25MB require manual re-upload

    Freshsales imposes a 25MB limit on individual file uploads, which is lower than what many LockedOn users store for property marketing. Video walkthroughs, high-resolution photography collections, large floor plans, and property condition reports frequently exceed this threshold. During migration, files over 25MB are flagged with a reference manifest that preserves their original metadata, file names, and record linkage. You receive this manifest after migration so you can re-upload the oversized files to Freshsales manually, maintaining the association to the correct record in Freshsales.

Migration approach

Six steps for a successful LockedOn to Freshsales data migration

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

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

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

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

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

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.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 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 Freshsales.

  • Object compatibility

    B

    2 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 Freshsales 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 Freshsales data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most LockedOn-to-Freshsales migrations complete in 48–72 hours of clock time for datasets under 50,000 total records. The longest planning step is usually the custom field setup on Freshsales for property-specific data migration. Larger setups with 500k+ records or complex vendor-property linking requirements extend the timeline to 5–7 days. Planning, custom field creation, the sample migration, and client sign-off typically add 1–2 days before the full run starts.

Adjacent paths

Related migrations to explore

Ready when you are

Move from LockedOn.
Land in Freshsales, 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