Migrate from LockedOn to HubSpot

LockedOn contacts map directly to HubSpot contacts. Phone, email, address, job title, and owner assignment carry over. Role type (buyer, vendor, tenant) is preserved as a custom contact property since HubSpot has no native role field. This ensures that contact-level segmentation and reporting in HubSpot reflect the original role classifications.

LockedOn tags on contacts migrate to HubSpot contact properties with type 'multiple-checkbox' or as a notes field. We preserve the full tag list per contact and note which tags were system-generated by LockedOn triggers. This approach lets you recreate tag-based automation in HubSpot workflows, using the preserved tags as conditions for enrollment.

LockedOn companies map to HubSpot companies. Company name, domain/website, industry, and employee count transfer as direct field maps. LockedOn's agency/organization-level records also land as HubSpot companies. Any additional company metadata, such as billing address or custom classifications, can be stored as custom company properties if needed for reporting.

LockedOn property listings become HubSpot deals. Listing price maps to deal amount. Listing status (Available, Under Offer, Sold) maps to HubSpot deal stage names via a value-mapping table. Property address, type, bedrooms, and bathrooms become custom deal properties. This transformation preserves the full property context within the deal record for downstream reporting and workflow automation.

Each LockedOn listing pipeline (e.g., Sales, Rental, Commercial) becomes a HubSpot deal pipeline. Pipeline stage names are mapped value-by-value to corresponding HubSpot stage names. Stage probabilities are re-applied based on HubSpot's stage configuration. If a LockedOn pipeline contains custom stages, those are recreated as new stages in HubSpot with the appropriate names and probability settings.

LockedOn tasks and action plan items migrate as HubSpot tasks. Original due dates, completion status, and task descriptions carry over. Owner resolution is performed by email match against HubSpot users. Incomplete tasks are flagged for re-assignment if no matching HubSpot user exists.

QR check-in records from LockedOn's open home feature have no native HubSpot equivalent. We migrate each OFI attendance as a HubSpot task linked to the contact with the inspection date, property, and attendee count preserved in custom fields. This preserves the open‑home history and enables follow‑up workflows based on attendance data.

LockedOn vendor reporting data — portal activity, feedback scores, listing performance summaries — requires a HubSpot custom object (available on Enterprise plans) or a structured note on the associated deal. We surface the recommended schema before migration. If your team opts for custom objects, we provide the field definitions and relationship mappings to ensure consistent data structure in HubSpot.

Documents attached to LockedOn contacts, companies, or property listings are re-uploaded to HubSpot Files and linked to the corresponding record. File size limits and inline image handling follow HubSpot's file attachment constraints. We also verify that file naming conventions are preserved to aid in record identification after migration.

LockedOn owner records are resolved against HubSpot users by email address. Unmatched owners are flagged before migration — your team can invite them to HubSpot or assign records to a fallback owner. Owner assignment history is preserved in the migrated record's audit trail.