Migrate from Launchpad CRM to monday CRM

Launchpad Client records map to Monday.com CRM Contacts. The primary contact fields (name, phone, email, address, demographics) migrate directly. Program enrollment status, eligibility flags, and compliance codes from the Client record migrate as Monday.com custom fields on the Contact. We deduplicate at migration time using the most recently updated field value because G2 reviewers report that the same client data must be entered multiple times across Launchpad modules.

Launchpad Case records link a Client to a Program and track service delivery, compliance milestones, and outcomes. Cases migrate to Monday.com Board Items organized by program group. Each Case Item carries a Contact lookup linking to the migrated Client record, preserving the client-to-case relationship. Compliance milestone fields and status transitions map to Monday.com status columns and date columns.

Launchpad Programs represent workforce development, SNAP, TANF, housing, or VR initiatives with eligibility rules and enrollment records. We assess whether to model Programs as Monday.com Board Groups (grouping Cases within a board) or as a Custom Object (Program) with a lookup relationship to Case Items, depending on the customer's reporting and filtering needs. The choice is confirmed during scoping based on HUD and RSA-911 reporting requirements.

Individual service encounters, assessments, and activities logged against a Case migrate as Monday.com Items or Subitems. Service type taxonomies from Launchpad may require value-mapping when the destination taxonomy differs. Assessment scores and completion dates migrate as numeric or date columns. Subitems are preferred when the customer needs per-encounter history within a Case item.

Uploaded files attached to Clients or Cases migrate as Monday.com file attachments or as integration links to the customer's existing Google Drive or SharePoint workspace. We preserve the document-to-record association during migration. File-type handling varies by destination storage tier; Enterprise Monday.com plans offer unlimited storage while Basic plans have storage limits that we validate during scoping.

Caseworker notes and case commentary migrate as Monday.com Item Updates or pulse notes on the linked Case Item. Rich-text formatting is preserved where the destination supports it. Notes are linked to the correct Contact and Case Item using Monday.com's relation columns.

Formal evaluations or skill assessments tied to a Case migrate as Monday.com custom fields (numeric, rating, or dropdown) on the Case Item. Assessment type taxonomy mapping may require field-level transformation when Launchpad and Monday.com use different value sets. Completion dates migrate as date columns.

Employer records used in job-placement workflows map to Monday.com CRM Companies. Employer name, industry, address, and contact information migrate as standard Company fields. We assess whether employer records need a separate Employer board or can live within the standard Monday.com Companies object based on the customer's job-placement workflow complexity.

Launchpad program-status or employment-placement stages map to Monday.com status columns and board groups. These do not map 1:1 to standard Monday.com CRM pipeline stages; we create a custom status column mapping table per migration. The customer confirms the stage sequence and any required-field gating during scoping so we can flag Monday.com limitations where certain columns cannot be made required across all board views.

Custom properties on any Launchpad object — eligibility flags, compliance codes, funding sources, program-specific attributes — migrate as Monday.com custom fields on the corresponding object. We preserve the API-compatible field name where possible. Field type mapping (dropdown to multi-select, text to number) is confirmed during scoping when Launchpad and Monday.com use incompatible type schemas.