Migrate from Launchpad CRM to Salesforce Sales Cloud

Launchpad Clients represent job seekers, benefit recipients, or program participants. We split at migration time using the client's employment-status and enrollment-status fields: clients with an active job-placement goal and an open Case map to Salesforce Lead; clients who are enrolled in a program with a assigned caseworker and documented outcomes map to Salesforce Contact attached to an Account. The split rule is designed during scoping with the customer's program staff and preserved as a custom field launchpad_original_status__c on both Lead and Contact for compliance audit.

Launchpad Client records that represent organizations (employers, training providers, or partner agencies) rather than individuals map to Salesforce Account. The client's organization name becomes the Account Name; the employer registration number becomes a custom field launchpad_employer_id__c. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert.

Launchpad Case records link a Client to a Program and track service delivery, compliance milestones, and outcomes. Cases map to Salesforce Case if the destination org includes Service Cloud licensing. Case status values (active, closed, pending compliance review) map to Salesforce Case Status picklist values. The caseworker assigned in Launchpad resolves to a Salesforce User by email match. Cases without a matching client record are held in a reconciliation queue.

Launchpad Programs represent workforce development, SNAP, TANF, housing, or VR initiatives with eligibility rules and enrollment records. These do not map 1:1 to any standard Salesforce object. We recommend a custom object launchpad_program__c with fields for program type, funding source, eligibility criteria, and enrollment date. Alternatively, if the organization tracks program outcomes as marketing cohorts, Salesforce Campaign is used with a custom Campaign Type value for workforce program. The customer chooses during scoping.

Launchpad enrollment records (client-to-program relationships) map to CampaignMember if Programs map to Campaigns, or to a custom junction object launchpad_enrollment__c with lookup fields to Contact and Program if using custom objects. Enrollment date, status, and completion date migrate as fields on the junction record. We pre-create the junction schema before migration so that enrollment inserts run after both Contact and Program inserts are complete.

Launchpad Service records represent individual service encounters, assessments, and activities logged against a Case. Service type taxonomy (skills assessment, job coaching, resume review, interview preparation) maps to Salesforce Task with a custom service_type__c picklist field. Duration and completion date preserve on the Task record. Services without a date are created as Tasks with no ActivityDate and flagged for follow-up scheduling.

Formal evaluations or skill assessments tied to a Case (CASAS, TABE, career aptitude, barriers to employment) require a custom object launchpad_assessment__c with fields for assessment instrument type, score, completion date, and expiration. We create the custom object schema before migration, including picklist values for instrument type and score bands. Assessment scores are stored as numeric fields for reporting; the original score string preserves in a custom field for audit.

Uploaded files attached to Clients or Cases migrate as Salesforce ContentVersion (file blob) and ContentDocumentLink (parent linkage). We download files from Launchpad CRM where accessible, upload to Salesforce via the Connect API, and re-associate using the ContentDocumentLink with the migrated Client (as Contact or Lead) or Case as the LinkedEntityId. File-type handling varies by Salesforce edition and storage limits.

Caseworker notes and case commentary migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Contact, Lead, or Case). Note body preserves as plain text; rich-text formatting in Launchpad converts to Salesforce rich-text Note where the destination supports it. Note timestamps preserve for activity timeline ordering.

Employer records used in job-placement workflows map to Salesforce Account with a custom record type of Employer. Employer name, industry, address, and hiring status migrate as Account fields. Employers without a hiring relationship to an active Case are flagged as inactive Accounts for follow-up. Employer-to-placement relationships migrate as custom Account fields or a junction object.

Launchpad compliance flags (eligibility status, federal reporting flags, verification pending, work-requirement exemption) migrate as custom fields on the Salesforce Case object: launchpad_eligibility_status__c, launchpad_federal_reporting_flag__c, launchpad_verification_status__c. We create these custom fields during schema design and map the values from Launchpad at migration time. These flags are critical for HUD and RSA reporting continuity and must not be dropped.

Launchpad program-status or employment-placement stages (intake, assessment, job-search, employed, closed) do not map 1:1 to standard Salesforce Case Status values. We create a custom picklist field launchpad_program_stage__c on Case with the exact stage labels from Launchpad. Stage transition timestamps migrate as separate custom date fields. The mapping table is built during scoping with the customer's program director.

Custom properties on any Launchpad object that capture program-specific data (funding source codes, referral source, barrier flags, work-experience type, vocational rehabilitation status) migrate as Salesforce custom fields on the equivalent destination object. We preserve the original field label and API name pattern (launchpad_ prefix) for traceability. Field types map from Launchpad types to Salesforce equivalents: text to Text, date to Date, picklist to Picklist or Multi-Select Picklist.

Caseworkers and staff accounts migrate as Salesforce User records by email match. Launchpad user roles (caseworker, supervisor, intake staff, program manager) map to Salesforce Profile or Permission Set assignments. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision. Inactive Launchpad users map to inactive Salesforce Users to preserve historical case assignments.