Migrate your LockedOn data
Cloud-based Real Estate CRM built for Australian agencies with automation, vendor reporting, and QR check-in for open homes. Small team, limited public API, opaque pricing.
In its favor
Why people choose LockedOn
The signal that keeps LockedOn on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Chosen by Australian real estate agencies for its all-in-one CRM, automation, and marketing platform that reduces manual follow-up tasks.
Customers appreciate the vendor reporting tools and 24/7 Vendor Portal, which keep sellers informed throughout the sales process without additional agent effort.
The QR check-in platform for open homes is cited as a modern feature that simplifies attendee registration at inspections.
Bulk communication and templating engine allows agencies to run on autopilot for routine client outreach and anniversary reminders.
Small team size means customers report a close relationship with support and straightforward onboarding for new agents.
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.
Reasons to switch
Why people leave LockedOn
The recurring reasons buyers give for replacing LockedOn. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where LockedOn fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
What gets migrated
LockedOn object support
Object-by-object support for LockedOn migrations. Per-pair details surface during scoping.
Contacts
Fully supportedLockeOn's primary contact object stores activity history, buying criteria, notes, and tags. We map contact fields directly and preserve the full activity log during migration.
Properties
Fully supportedProperties track the full lifecycle from potential to sold, including marketing materials, portal uploads, documents, and associated activities. We preserve this lifecycle metadata across migrations.
Listings
Fully supportedListings are tied to Properties and include status, details, and marketing assets. We map Listings to the destination's equivalent object and flag any missing required fields.
Vendors
Fully supportedVendor records include contact details and are associated with Properties being sold. We map Vendor fields directly and preserve the vendor-property linkage.
Tenants
Mapping requiredTenant records hold lease-related data including lease terms and tenancy status. We map Tenant fields but flag that lease-specific fields may require manual verification on the destination platform.
Leases
Mapping requiredLease records include terms, start/end dates, and associations to Tenants and Properties. The mapping depends on the destination CRM's lease object schema, and we flag discrepancies during scoping.
Automations (Triggers and Task Plans)
Not in this platformLockeOn's automation rules including OFI follow-up triggers, post-enquiry welcome sequences, and task plan templates are not exportable via a documented public API. We do not migrate these; they must be manually rebuilt on the destination platform.
Documents
Mapping requiredDocuments attached to Properties, Contacts, or Leases can be extracted and reattached in the destination system. We handle file export and re-upload but preserve document-to-record associations explicitly.
Tags and Custom Fields
Mapping requiredTags on Contacts and Properties are migrated as-is. Custom fields are migrated with their values but may require manual reconfiguration on the destination if field types differ.
Vendor Portal Records
Not in this platformThe 24/7 Vendor Portal is a LockeOn-specific feature that cannot be replicated on most destination platforms. We do not migrate portal access; we export the underlying Vendor data for manual reassignment.
QR Check-in Data
Not in this platformQR check-in records from open homes are tied to LockeOn's event-check-in module and are not independently exportable. We do not migrate this object.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | LockeOn's primary contact object stores activity history, buying criteria, notes, and tags. We map contact fields directly and preserve the full activity log during migration. |
| Properties | Fully supported | Properties track the full lifecycle from potential to sold, including marketing materials, portal uploads, documents, and associated activities. We preserve this lifecycle metadata across migrations. |
| Listings | Fully supported | Listings are tied to Properties and include status, details, and marketing assets. We map Listings to the destination's equivalent object and flag any missing required fields. |
| Vendors | Fully supported | Vendor records include contact details and are associated with Properties being sold. We map Vendor fields directly and preserve the vendor-property linkage. |
| Tenants | Mapping required | Tenant records hold lease-related data including lease terms and tenancy status. We map Tenant fields but flag that lease-specific fields may require manual verification on the destination platform. |
| Leases | Mapping required | Lease records include terms, start/end dates, and associations to Tenants and Properties. The mapping depends on the destination CRM's lease object schema, and we flag discrepancies during scoping. |
| Automations (Triggers and Task Plans) | Not in this platform | LockeOn's automation rules including OFI follow-up triggers, post-enquiry welcome sequences, and task plan templates are not exportable via a documented public API. We do not migrate these; they must be manually rebuilt on the destination platform. |
| Documents | Mapping required | Documents attached to Properties, Contacts, or Leases can be extracted and reattached in the destination system. We handle file export and re-upload but preserve document-to-record associations explicitly. |
| Tags and Custom Fields | Mapping required | Tags on Contacts and Properties are migrated as-is. Custom fields are migrated with their values but may require manual reconfiguration on the destination if field types differ. |
| Vendor Portal Records | Not in this platform | The 24/7 Vendor Portal is a LockeOn-specific feature that cannot be replicated on most destination platforms. We do not migrate portal access; we export the underlying Vendor data for manual reassignment. |
| QR Check-in Data | Not in this platform | QR check-in records from open homes are tied to LockeOn's event-check-in module and are not independently exportable. We do not migrate this object. |
Gotchas
What to watch for in LockedOn migrations
Issues we've hit on past LockedOn migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving LockedOn?
Where LockedOn customers move next
12 destinations LockedOn can migrate to.
How a LockedOn migration works
Four steps, LockedOn-specific
Connect
Not publicly documented into LockedOn. Scopes limited to read-only on the data we move.
Map
We translate LockedOn-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate LockedOn quirks before production.
Migrate
Full migration with LockedOn rate-limit handling. Rollback available throughout.
FAQ
LockedOn migration FAQ
Answers to the questions buyers ask most during LockedOn migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your LockedOn migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate LockedOn.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your LockedOn setup and destination — written quote back within a business day.