Migrate from Launchpad CRM to Microsoft Dynamics 365 Sales

Launchpad Clients (job seekers, benefit recipients, program participants) map to Dynamics 365 Contact records. If the Client has an associated employer or referral organization, we also create an Account record and link it via the AccountId lookup. Client demographics, contact information, and eligibility flags migrate as Contact fields; program-specific compliance data migrates to custom fields on Contact. Address data splits into Dynamics standard address fields with a migration note if multiple service-location addresses exist per Client.

Launchpad Cases link a Client to a Program and track service delivery, compliance milestones, and outcomes. For workforce agencies that track program participation (not commercial sales), we configure a custom Case entity in Dynamics 365 that mirrors the Launchpad schema with Client lookup, Program lookup, status transitions, and milestone dates. For agencies with placement outcomes that resemble sales cycles, Cases map to Opportunity with the Client as the primary Contact and a custom enrollment record capturing program-specific fields.

Launchpad Programs (workforce development, SNAP, TANF, housing, VR initiatives) with eligibility rules and enrollment records require a custom Program entity in Dynamics 365. We pre-create the Program schema in Dataverse including eligibility criteria fields, funding source codes, and program duration fields before any data import. If Programs have associated services with unit costs or grant allocations, we create Product2 records to track service-line billing or voucher redemption.

Individual service encounters, assessments, and activities logged against a Case map to a custom Service Encounter entity linked to the Case record. Service type taxonomies (assessment, counseling, job placement, training) value-map from Launchpad to the destination taxonomy during the transform step. Assessment scores and completion dates migrate; instrument-type mapping may require field-level transformation if the destination assessment framework differs from the source.

Launchpad document blobs attach to Clients or Cases. We migrate file content and re-associate to the correct parent record in Dynamics 365. The recommended destination is SharePoint Online integrated via Dynamics 365's native SharePoint document management, which gives caseworkers familiar Office 365 access patterns. File-type handling, naming conventions, and folder hierarchy are preserved as closely as the destination SharePoint structure allows.

Caseworker notes and case commentary migrate as Dynamics 365 Note records (Annotation) linked via regardingObjectid to the parent Contact, Account, Case, or custom Program record. Plain-text notes migrate directly; rich-text or formatted notes are flagged for manual review because Dynamics Annotation has limited formatting support compared to some source systems.

Formal evaluations or skill assessments tied to a Case migrate to a custom Assessment entity with fields for assessment type, score, completion date, and instrument name. We value-map assessment instrument types from the Launchpad taxonomy to the destination taxonomy during the transform step. Historical assessment scores are preserved; any scoring rubric or normalization that existed in Launchpad is noted for the customer to rebuild as a Power BI report post-migration.

Launchpad Employer records used in job-placement workflows map to Dynamics 365 Account records with the employer name, industry, address, and contact information. We flag any employer that is also a Client (a job seeker who became a placement employer) for the customer to resolve as a duplicate Account or as a separate record with a type indicator. This N:1 pattern is common in workforce programs and requires explicit customer confirmation during scoping.

Launchpad program-status or employment-placement stages do not map 1:1 to standard Dynamics 365 Opportunity stages (Prospecting, Qualification, Needs Analysis, Value Proposition, Id. Decision Makers, Perception Analysis, Proposal/Price Quote, Negotiation/Review, Closed Won, Closed Lost). We create a custom stage mapping table per migration that maps Launchpad stage values to either custom Opportunity stages or to status values on the custom Case entity, depending on the chosen case model.

Launchpad custom properties on any object — eligibility flags, compliance codes, funding sources, caseworker assignments, program-specific attributes — migrate to Dynamics 365 custom fields on the corresponding entity. We pre-create the destination schema in Dataverse before any data import, matching API names with a __c suffix per Dynamics convention and mapping field types (text, integer, picklist, date, boolean) from the source extraction.