Migrate from LockedOn to Twenty CRM

LockedOn contacts represent individual clients (buyers, sellers, tenants). They map directly to Twenty's People object. The contact's primary company link in LockedOn becomes the companyId relation in Twenty after Companies are imported. LockedOn contact tags migrate as custom multi-select fields in Twenty.

LockedOn companies represent agencies, property management firms, landlords, and property owners. These entities map directly to Twenty's Companies object. Company hierarchies in LockedOn (parent-branch relationships) transfer to Twenty's self-referential companyId relation, preserving organizational structures. Industry classification pick-list values map value-by-value from LockedOn's industry field to Twenty's industry field, maintaining consistent categorization across the migration.

LockedOn's property records (listing details, property type, address, status) have no direct equivalent in Twenty's standard Opportunity object. We create a Property custom object in Twenty and migrate fields including address components, property type, listing status, and price. The property links to its owning Company and to related People (agents, owners).

LockedOn deals tied to specific properties map to Twenty Opportunities with a relation to the migrated Property custom object. The deal's commission amount, expected close date, and stage (Offer Made, Under Contract, Settled) map to Opportunity amount, closeDate, and stageName. If LockedOn uses multiple pipelines, we create separate stage sets in Twenty.

LockedOn tasks and action items map directly to Twenty's Tasks object. Task due dates, assignees (matched by email to Twenty workspace members), completion status, and linked records (contact, property, deal) are preserved. Completed task timestamps are stored as custom datetime fields since Twenty's default completedAt may not reflect the original completion date.

LockedOn notes attached to contacts, companies, or properties migrate to Twenty Notes. Notes are linked to the parent record (People, Company, or Property custom object) via the noteableId relation. Rich-text formatting in LockedOn notes is preserved where the format is compatible with Twenty's note rendering.

LockedOn engagement records (calls logged, emails recorded, meetings scheduled) are stored as Twenty Tasks with Type set to Call, Email, or Meeting. Original activity timestamps and the user who logged the activity are preserved. Activity body text maps to the Task body field.

LockedOn's Triggers (OFI follow-up, post-enquiry welcome) and Plan/Automation templates have no equivalent in Twenty CRM. These configurations are exported as JSON documentation briefs that your Twenty admin can use to rebuild equivalent Workflows in Twenty's Settings → Workflows. We document the trigger event, conditions, and resulting actions for each active trigger.

LockedOn's bulk communication templates (email/SMS templates for agent outreach) do not migrate. We export the template body text and variable placeholders as a CSV that can be imported into your preferred email tool or rebuilt as Twenty Workflow email actions. Twenty itself has no native bulk email feature.

LockedOn's vendor reporting portal and seller-facing 24/7 portal configurations are platform-specific and have no Twenty CRM equivalent. This feature must be re-evaluated post-migration — either through Twenty's API + a custom front-end, or by selecting a separate vendor portal tool.

LockedOn's QR check-in for open homes is a property-industry-specific feature with no Twenty CRM equivalent. If your team relies on this for event registration at property inspections, it must be handled by a separate tool or rebuilt as a custom integration on top of Twenty's API.

LockedOn custom properties on any object migrate as Twenty custom fields. We create each custom field under Settings → Data Model before importing data, matching the field type (text, number, date, select, multi-select). Select field options are mapped value-by-value. Custom properties with dependencies (e.g., conditional visibility in LockedOn) are documented for manual reconfiguration in Twenty.

LockedOn users (agents, admin staff) are resolved by email match against Twenty workspace members. We require your Twenty workspace to be set up and members invited before migration so user references on records can link correctly. Unmatched owners are flagged with a fallback assignment for your review.