Migrate from Launchpad CRM to HighLevel

Launchpad Client records map to GoHighLevel Contact. The primary person record (name, email, phone, address, demographics) migrates directly. We preserve program eligibility flags, compliance codes, and any demographic fields as Contact Custom Fields in GoHighLevel. Deduplication is applied where the same person appears as both a Client and within a Case record due to Launchpad's redundant-entry pattern; we use the most recently updated field value as the canonical source.

Launchpad Case records map to GoHighLevel Opportunity. The case-to-program linkage migrates as a GoHighLevel Opportunity custom field (e.g., Program_Enrollment__c) and the case status maps to the relevant Pipeline Stage. Case-level compliance milestones and outcomes migrate as Opportunity custom fields. We create a GoHighLevel Pipeline named 'Program Enrollment' or similar to hold these records, distinct from any sales pipeline the organization also uses.

When a single Client has multiple active Cases across different Programs, we create a GoHighLevel Opportunity per Case and link all Opportunities to the same Contact record. The Case-to-Client parent relationship is preserved through Contact lookup on each Opportunity. Program start and end dates migrate as custom date fields on the Opportunity.

Launchpad Program definitions (workforce development, SNAP, TANF, housing, VR) do not have a direct GoHighLevel equivalent because GoHighLevel does not have a native program enrollment object. We map Programs to a Contact Custom Field (Primary_Program__c) with a picklist of the customer's active programs, and we map enrollment status to an Opportunity Custom Field (Enrollment_Status__c) with values mapped from Launchpad case status.

Individual service encounters, assessments, and activities logged against a Launchpad Case migrate to GoHighLevel as Task records linked to the parent Opportunity (which represents the Case). Service type taxonomy from Launchpad maps to Task Subject or a custom Task field (Service_Type__c) as a picklist. Assessment scores and completion dates migrate as custom fields on the Task.

Uploaded files attached to Clients or Cases in Launchpad transfer as GoHighLevel attachments. We preserve the parent record linkage (Contact for Client-level documents, Opportunity for Case-level documents). File-type handling varies by GoHighLevel's attachment model; PDFs and images migrate directly; linked external URLs are preserved as text fields on the parent record.

Caseworker notes and case commentary from Launchpad migrate to GoHighLevel Notes linked to the parent Contact or Opportunity. Rich text migrates as plain text with any embedded references preserved. Notes are imported after the parent Contact and Opportunity records to satisfy linkage requirements.

Employer records used in job-placement workflows map to GoHighLevel Contacts with a Contact Type of 'Company' or 'Business'. We create the employer as a separate Contact record (type Business) and link any job-seeking Clients as separate Contact records (type Person). GoHighLevel does not have a standalone Company object; organizations that need formal Account-Contact hierarchy may require a GoHighLevel Marketplace app for multi-contact business entities.

Launchpad custom fields on any object (eligibility flags, compliance codes, funding sources, program-specific properties) migrate to GoHighLevel Custom Fields. We distinguish between Contact Custom Fields (for fields that belong to the person record) and Opportunity Custom Fields (for fields that belong to the case or enrollment). GoHighLevel requires custom fields to be created in the destination before data import; we provision them during the schema design phase.

Caseworker and staff accounts migrate to GoHighLevel Users by email match. We extract every distinct Launchpad Owner referenced on Client, Case, and Service records and map to the destination GoHighLevel User. Users without a matching GoHighLevel account go to a reconciliation queue for the customer's admin to provision before record import resumes. Case assignments migrate as Opportunity ownership after User mapping is validated.