Migrate from LeadManaging to HighLevel

LeadManaging lead and contact records map directly to HighLevel Contacts. Leasing-status metadata from LeadManaging preserves as a custom picklist field (Leasing_Status__c) since HighLevel uses tags for segmentation. All contact fields — name, email, phone, address — map 1:1 to HighLevel contact properties.

LeadManaging company and property records map to HighLevel Companies. Property name, address, unit count, and leasing-company details migrate as Company custom fields. Parent-company relationships in LeadManaging map to HighLevel's Company hierarchy via a Parent Company custom field. If a property has multiple parent companies, we create separate Parent_Company__c entries for each relationship, preserving the full hierarchy in HighLevel's company records.

LeadManaging lease deals map to HighLevel Opportunities. Deal amount, stage, close date, and owner migrate to the corresponding HighLevel Opportunity fields. LeadManaging's lease-stage pipeline values map to HighLevel pipeline stage values by name with probability mapping per stage. If a deal has multiple owners in LeadManaging, we assign the primary owner by email and record secondary owners in a custom multi-user field on the Opportunity.

LeadManaging custom fields — lease type, bedroom count, move-in date, budget range — require manual creation in HighLevel as custom fields before migration runs. We deliver a custom-field setup checklist with field names, types, and picklist values so your team pre-creates the schema before data lands.

LeadManaging tags and labels migrate as HighLevel Tags, which drive segmentation, workflow triggers, and contact filtering. Tags preserve exactly as exported — no transformation required. N:N tagging is natively supported in HighLevel's tag model. If you have hierarchical tags, we map them to flat HighLevel tags while preserving the original hierarchy name in the tag description for reference.

LeadManaging file attachments on contacts or companies download and re-upload to HighLevel's file storage. File name, size, and upload date are preserved. Inline images in notes download separately and rehost within HighLevel's note attachments. We also verify file type compatibility, converting any unsupported formats to HighLevel-supported alternatives before upload to prevent playback issues.

LeadManaging notes and comments map to HighLevel Notes. Original timestamps, note authors, and parent-record links (contact or company) are preserved. Rich-text formatting in LeadManaging notes converts to HighLevel's note format. If a note contains embedded images or attachments, we extract them and attach them separately in HighLevel, ensuring that visual context is retained.

LeadManaging owner assignments resolve by email match to HighLevel user accounts. Unmatched owners flag before migration — your team either invites them to HighLevel first or assigns records to a fallback user. No record lands in HighLevel without an assigned user.

LeadManaging custom objects map 1:1 to HighLevel Custom Objects via the HighLevel API v2.0. Custom object schemas are recreated in HighLevel before migration. Relationships between custom objects and contacts or companies use HighLevel's relationship fields — N:N relationships require junction object setup.

LeadManaging activity history — view logs, email opens, form submissions — migrates as HighLevel contact activities with original timestamps preserved. This provides continuity for sales and leasing teams reviewing prospect engagement history in HighLevel. If an activity type does not map directly to a HighLevel activity category, we create a custom activity type with the original label for accurate reporting.