Migrate from improveit 360 to HighLevel

improveit 360 contacts map directly to HighLevel contacts. All standard fields (name, email, phone, address) transfer as-is. Owner assignment resolves by email match against HighLevel users — unmatched owners receive a fallback assignment and are flagged for admin review before final migration commits.

improveit 360 leads (the Salesforce Lead object) map to HighLevel contacts. In HighLevel's model there is no separate Lead object — all person records are Contacts. We transfer lead status, source, and rating as contact custom fields since HighLevel has no native lead-status pick-list equivalent.

improveit 360 accounts map to HighLevel businesses. Business name, website, industry, employee count, and annual revenue transfer directly. improveit 360 stores parent-child account hierarchies using Salesforce ParentId — we replicate this as a Primary Business relationship on the HighLevel contact record. Multi-business contacts collapse to one primary business with additional relationships surfaced as tags.

improveit 360 opportunities map to HighLevel opportunities. The opportunity name, amount, close date, and stage name transfer. Stage values are mapped via value_mapping — each improveit 360 pipeline stage maps to a corresponding HighLevel pipeline stage. Owner assignment resolves by email match, same as contacts.

improveit 360 pipelines (Salesforce Sales Processes tied to record types) become HighLevel pipelines. Each improveit 360 pipeline generates one HighLevel pipeline. Stage names are mapped value-by-value. If improveit 360 uses multiple record types for different deal categories (e.g., one for replacements, one for new construction), each record type becomes a separate HighLevel pipeline to preserve stage-scoping logic.

improveit 360 tasks transfer to HighLevel tasks with subject, status, priority, and due date preserved. Original timestamps and assigned owner map by email resolution. HighLevel tasks attach to the corresponding contact or opportunity record by looking up the source record ID stored in a custom field during migration.

improveit 360 events (meetings, calls, appointments) map to HighLevel appointments. Start time, end time, location, subject, and related contact transfer. HighLevel's appointment scheduling feature is separate from the CRM task model — appointments land in the Calendars module linked to the contact record for scheduling continuity.

improveit 360 notes map to HighLevel notes. Rich-text formatting is preserved where HighLevel's note editor supports it. Notes attach to the parent contact or opportunity using a lookup based on the source record ID. Created date and author transfer for audit continuity.

improveit 360 file attachments on records download from Salesforce storage and re-upload to HighLevel Files. File size limits apply — HighLevel's default file size cap is 25MB; files exceeding this are flagged and require either compression or a file-hosting link stored as a custom field reference in HighLevel.

improveit 360's Salesforce __c custom fields require destination field creation in HighLevel. We determine field type (text, number, date, pick-list, checkbox, etc.) from the Salesforce field metadata and create the equivalent in HighLevel. Contact-level improveit 360 fields become HighLevel Contact Custom Fields; opportunity-level fields become HighLevel Opportunity Custom Fields — this distinction matters because HighLevel does not allow field-type switching after creation.

improveit 360's project management module (job costing, production grid, scheduling) has no direct HighLevel equivalent. Project headers map to a HighLevel custom object if the project has significant data; project line items and cost breakdowns map to Opportunity Custom Fields. Scheduling dependencies require manual rebuild in HighLevel's calendar tools.

improveit 360's automated sales quoting with mobile support and contract documents has no native HighLevel equivalent. Quote line items, pricing tiers, and approval routing must be rebuilt using HighLevel Opportunities with Products or Opportunity Custom Fields. We preserve quote data as a reference attachment and export the quote definitions as a rebuild specification.