Migrate from LockedOn to HighLevel

LockedOn contacts map directly to HighLevel contacts. Name, email, phone, address, and custom properties migrate as-is. Owner assignment resolves by email match to a HighLevel user account; unmatched owners are flagged before the migration commits. Each contact preserves its original creation timestamp in a custom field for reporting continuity, and the LockedOn record ID is stored on the HighLevel contact for traceability and delta-run de-duplication.

LockedOn contacts can associate with multiple properties through an N:N relationship. Since HighLevel lacks a native junction for Contact-to-Custom-Object associations, we create a junction Custom Object (e.g., Contact_Property_Link__c) with ContactId and PropertyId lookups to preserve the many-to-many link. This approach maintains full association integrity across the migration while respecting HighLevel's object architecture.

LockedOn companies (agencies, property management firms, landlords) map to HighLevel companies. Company name, address, domain, and custom fields migrate directly. Companies without contacts are flagged so they can be reviewed before landing in HighLevel. The company type field (Agency, Property Manager, Landlord, Developer) maps to corresponding custom company type values in HighLevel.

LockedOn's native Property object has no HighLevel equivalent. Properties become a Custom Object named 'Property' with custom fields for address, property type, listing status, price, bedrooms, bathrooms, and buyer criteria. The object must be created in HighLevel before migration — we deliver a schema setup plan before data moves.

LockedOn deals representing property transactions map directly to HighLevel Opportunities. Deal name, amount, stage, close date, and owner migrate as-is. Deal pipelines map to HighLevel pipeline stages with value-by-value mapping for stage names and probability weights. The LockedOn deal ID is preserved in a custom field for traceability, and the property association links to the Property Custom Object via a lookup field.

LockedOn pipeline stages (e.g., 'Active', 'Under Offer', 'Settled') map to HighLevel pipeline stages by name. Probability weights and forecast categories are applied based on the source stage values. Stage transition timestamps are preserved as custom datetime fields on the Opportunity record.

LockedOn Triggers (OFI follow-up, post-enquiry welcome, vendor reporting) are automation logic with no direct HighLevel equivalent. We export trigger definitions as a text reference for your HighLevel admin to rebuild in the Workflow Builder. The data inside the Trigger (the tasks it creates, the conditions it checks) does not migrate — only the trigger name and rule structure for documentation.

LockedOn tasks and automated action plans migrate as HighLevel tasks. Original due dates, assignees, and completion status are preserved. Tasks generated by LockedOn Triggers are included if they were explicitly created before the migration window. Task status values (Pending, Completed) map to HighLevel task status values by name for accurate state preservation.

LockedOn tags migrate to HighLevel tags as-is. Tag names and the contact/tag associations are preserved. Tags used for lead segmentation or pipeline routing in LockedOn are flagged so HighLevel workflows can be configured with equivalent trigger conditions. The migration includes all tag-to-contact linkages to maintain segmentation integrity in the new system.

LockedOn engagement history including calls, emails, meetings, and notes migrates as HighLevel Activities attached to the relevant contact or opportunity record. Original timestamps, owners, and subject lines are preserved. Attachments are re-uploaded to HighLevel's file storage. Activity type (Call, Email, Meeting, Note) maps to the corresponding HighLevel Activity type field.

LockedOn QR check-in records (attendee name, property, date, feedback) have no HighLevel equivalent. They migrate as entries in a 'Open_Home_Attendance' Custom Object with contact lookup and event details as custom fields. The QR check-in workflow itself (the mechanism, not the data) must be rebuilt using HighLevel's form and workflow triggers.

LockedOn bulk communication templates and the templating engine do not migrate. Email and SMS templates are not part of the data export. We can export template content as a text reference for manual rebuild in HighLevel's template editor. Template variables (%contactname%, %propertyaddress%) require translation to HighLevel's merge field syntax.

LockedOn's automated vendor reporting and 24/7 Vendor Portal have no HighLevel equivalent. Vendor report data (listing updates, buyer feedback, inspection results) can be preserved in a Custom Object, but the automated delivery and portal access must be rebuilt using HighLevel's Workflows and Client Portal add-on. We document the source report fields for your admin to replicate.