Migrate from Function 365 to HighLevel

Function 365 contact records map directly to HighLevel contacts. Every contact field (name, email, phone, address) transfers as-is. Contacts linked to companies use the company_id lookup — we ensure the company record exists in HighLevel before contacts land so the relationship is preserved.

Function 365 company records map to HighLevel businesses. Company name, domain/website, industry, employee count, annual revenue, phone, and address fields transfer to the matching HighLevel business fields. Multi-location companies from Function 365 become multiple Business records, each tagged to preserve location grouping within HighLevel.

Function 365 deals with stage, amount, close date, and owner map to HighLevel Opportunities. The critical transformation is mapping Function 365 deal stages to HighLevel pipeline stage pick-lists — each distinct stage value in Function 365 requires a corresponding stage in the target HighLevel pipeline before mapping can proceed.

Function 365 pipelines map to HighLevel pipelines 1:1. Each pipeline in Function 365 becomes a separate pipeline in HighLevel with its own set of stage values. We extract all pipeline names and stage definitions from Function 365 before creating the corresponding pipeline structure in HighLevel.

Function 365 tasks migrate to HighLevel tasks with subject, due date, assigned user, and completion status preserved. The original task owner is resolved by email match against HighLevel users. Open tasks in Function 365 land as open tasks in HighLevel; completed tasks retain their completion timestamps.

Function 365 notes map to HighLevel notes with body text, associated contact or deal link, and creation timestamp preserved. Rich-text formatting in Function 365 notes is simplified to plain text in HighLevel notes. Notes without a parent record attach to the contact specified in the migration plan.

Function 365 user records resolve to HighLevel users by email address. Active users in Function 365 become active users in HighLevel. Inactive or archived users are flagged for review — they can be invited to HighLevel before migration or assigned as a fallback owner for records where the original assignee does not exist in HighLevel.

Any custom fields on contacts, companies, or deals in Function 365 require a corresponding custom field to be created in HighLevel before migration. We extract the full custom-field schema — field name, data type, pick-list values — and create matching custom fields in HighLevel as part of the pre-migration setup phase.

Function 365 tags applied to contacts or companies migrate as HighLevel tags. Tags represent behavioral or categorical labels (e.g., 'hot-lead', 'enterprise') and transfer as a flat list. If a contact in Function 365 has multiple tags, all of them are applied to the corresponding HighLevel contact.

Function 365 quotes or estimates do not have a native equivalent in HighLevel's base CRM. Quotes migrate as attachments linked to the Opportunity record, preserving the document content for reference. HighLevel's Products feature can be used to recreate line items manually after migration.

Call logs, emails, and meeting records from Function 365 surface as activity entries linked to the contact in HighLevel. Each activity type (call, email, meeting) maps to its corresponding HighLevel activity type. Original timestamps and activity owners are preserved in the migration.

Workflows and automation rules in Function 365 do not migrate — they must be rebuilt in HighLevel's Workflow builder. We export a machine-readable summary of your Function 365 workflow definitions (trigger events, conditions, actions) as a rebuild reference so your team can reconstruct each automation in HighLevel with equivalent logic.