Migrate from RecruitBPM to Crelate

RecruitBPM Candidates map 1:1 to Crelate Contacts. We preserve resume data, contact details, skills, certifications, source attribution, and status. Candidate skill tags and certifications map to Crelate's skill and certification fields on the Contact record. Source attribution (Indeed, LinkedIn, referral, etc.) migrates to the Source field. During scoping we extract all custom field definitions on the Candidate object and map each to either a Crelate standard Contact field or a custom field created via Settings > Custom Forms with field mapping per question.

RecruitBPM Clients (the organizations a staffing agency places talent into) map directly to Crelate Companies. We preserve company name, industry, location, relationship notes, and primary contact details. Client contact details from RecruitBPM map to Crelate Company contacts. During scoping we confirm whether each Client has a primary Contact record or just organizational data and configure the mapping accordingly.

RecruitBPM Job Orders (positions the agency is recruiting for) map to Crelate Opportunities. We preserve job title, requirements, compensation range, location, and the pipeline stage progression. The Job Order to Opportunity mapping requires resolving the parent Client (Company) and any associated Placement (if filled) at migration time. RecruitBPM's customizable pipeline stages map to Crelate's Sales Process and Opportunity stage values, which we configure before migration.

RecruitBPM Placements (confirmed hires) map to Crelate Opportunities with stage set to Closed Won, linked to the Candidate (Contact) and Client (Company). We preserve start date, placement fee, compensation details, and the billing history tied to the placement. Placement fee and compensation amounts migrate to Opportunity Amount and related custom fields. Activity records attached to the placement (offer letters, onboarding notes) migrate as Crelate Activity records linked to the Opportunity.

RecruitBPM Talent Pools are segregated candidate collections by skill, location, or certification used for rapid engagement. We preserve pool membership and the relationship to each Candidate. Crelate's tagging system or custom lists (maintained via bulk edit) serve as the equivalent. Pool names migrate as tags on the relevant Contact records, and we provide a written reference mapping each pool name to its constituent contacts for the customer's admin to validate in Crelate.

RecruitBPM Interview records (scheduled time, interviewer, format, outcome notes) map to Crelate Events with StartDateTime, EndDateTime, and Location preserved. Interview outcome and feedback notes migrate to Event description or to a Crelate Activity Form. For recorded video interviews, the video file migrates as a Crelate attachment linked to the relevant Contact and Opportunity; we verify file format compatibility during scoping.

RecruitBPM Assessments (custom forms and evaluations administered during screening) migrate as Crelate Activity Forms with responses preserved as structured data. Custom form schema definitions are documented separately since Crelate's Activity Form builder uses a different structure. Assessment scores and evaluation results migrate to the Contact record via Crelate's field mapping feature, which copies form answers to typed fields on the parent Contact record. The customer reviews form layout after migration and may choose to recreate the form in Crelate's Activity Form builder.

RecruitBPM tracks emails, calls, SMS, voicemails, and notes as activity records tied to Candidates and Clients. Crelate uses Activity records with Activity Forms for structured data capture. We map common activity types: email calls to Crelate Email activity records, phone calls to Crelate Call activity records with disposition and duration, notes to Crelate Note records linked via ContentDocumentLink to the parent Contact or Company. RecruitBPM's proprietary activity type taxonomy requires transformation during the migration extract phase.

RecruitBPM's customizable pipeline stages per Job Order map to Crelate's Sales Process configuration. Each pipeline in RecruitBPM becomes a Sales Process in Crelate with corresponding stage values. Stage names, order, and probability percentages migrate. We configure Crelate's Sales Process and stage whitelist during the pre-migration configuration phase so that incoming Opportunities land in the correct stage by pipeline.

RecruitBPM's tenant-specific custom field schemas (defined across Candidates, Clients, and Job Orders) require individual extraction and mapping during scoping. We extract the full field definition set, identify the equivalent Crelate field type (text, number, date, picklist, checkbox, etc.), and create custom fields via Crelate's Custom Forms settings. Custom field dependencies on workflows or triggers are documented separately since workflow logic does not migrate. The customer's admin validates custom field data integrity in Crelate's staging environment.

RecruitBPM platform users who own records and drive workflows map to Crelate Users. We resolve owner assignments by email match during migration. Any RecruitBPM user without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision. Permissions and team structure hierarchies do not migrate programmatically; we document the original permission model as a reference for Crelate configuration.

Resume files, contracts, onboarding documents, and other attachments stored in RecruitBPM migrate as binary blobs into Crelate's file attachment system. We verify file format compatibility (PDF, DOCX, TXT, common image formats) during scoping and flag any unsupported formats. Files are linked to the correct parent record (Contact for resumes, Company for client contracts, Opportunity for job order documents). Crelate's Resume Toolbox feature at Business tier provides structured parsing of uploaded resume files.