Migrate from Launchpad CRM to Twenty CRM

Launchpad Client records map to Twenty People. The primary contact fields (name, phone, email, address) map directly. Program eligibility flags, compliance codes, and demographics stored as custom fields on the Client record become Twenty custom fields on People, created via Settings -> Data Model before import. We deduplicate records where the same person appears in multiple modules by preferring the most recently updated field value.

Launchpad Case records map to Twenty Opportunity. The case-to-client relationship becomes the Opportunity's People (contact) lookup. Case status, compliance milestones, and outcomes map to Opportunity stage and custom fields. We create a custom Opportunity stage mapping table that reflects the customer's case lifecycle rather than a sales pipeline.

Launchpad Program definitions (workforce development, SNAP, TANF, housing, VR) map to Twenty Custom Objects named Programs. We pre-create the Custom Object via the /metadata API before import, defining fields for eligibility rules, funding sources, and enrollment windows. The Program-to-Case relationship becomes a lookup field on the Opportunity (Case) record.

Individual service encounters and assessments logged against a case map to Twenty Notes attached to the parent Opportunity record, or to a custom Service Encounter object if the customer uses a structured service taxonomy. Service type value maps may be needed when Launchpad's taxonomy differs from Twenty's select options.

Launchpad Employer records used in job-placement workflows map to Twenty Company. Employer name, industry, address, and contact information migrate as standard Company fields. The employer-to-case placement relationship becomes a Company lookup on the Opportunity record.

Uploaded files attached to clients or cases transfer as file blobs and re-associate to the correct parent record in Twenty. File-type handling depends on Twenty's attachment model at the time of migration. Documents are the last object processed because they often reference already-migrated parent records.

Formal evaluations and skill assessments tied to a case map to a Twenty Custom Object named Assessment with fields for assessment type, score, completion date, and evaluator. Instrument-type mapping may require value transformation when assessment taxonomies differ between Launchpad and Twenty.

Caseworker notes and case commentary migrate as Twenty Note records linked via ContentDocumentLink to the parent People, Opportunity (Case), or Company record. We migrate as plain text where rich text formatting does not apply.

Program-status or employment-placement stages do not map 1:1 to standard sales pipeline stages. We create a custom select field on the Opportunity object with stage values that match the customer's case lifecycle. The mapping table is built during scoping and validated in a test migration before production.

Caseworkers and staff accounts migrate as Twenty Members. We invite all users as Twenty Members via Settings -> Members before importing any records with ownership references, because Twenty requires the target user to exist before owner lookups can resolve. We match by email address and flag any Launchpad user without a matching email in the destination workspace.

Custom properties on any Launchpad object (eligibility flags, compliance codes, funding sources) migrate as Twenty custom fields. All custom fields must be created in Settings -> Data Model before CSV import runs, because Twenty's CSV import creates records only, not fields. We create them in the correct object and with the correct field type (text, number, date, select, multi-select, relation) during the setup phase.