Migrate from mploy to Crelate

mploy Candidates map directly to Crelate Candidates. Standard fields include name, email, phone, and resume. Because mploy has no confirmed API, we export via admin-panel CSV and validate field counts against Crelate after import. Custom fields on Candidates must be explicitly enumerated by the customer during discovery before mapping can begin. Resume files may require a separate file archive export if not included in the bulk download; we confirm this before finalizing the migration scope.

mploy Jobs (open positions) map to Crelate Jobs with fields for title, department, location, description, and status (active/closed). Active and archived jobs both migrate to preserve closed requisition history. Job status (open vs. closed) maps to Crelate's Job Status field, and any custom fields on Jobs require the same enumeration process as Candidate custom fields.

mploy Applications are the join records linking Candidates to Jobs, capturing submission date, current stage, and source attribution. Source attribution and stage names frequently differ between ATS systems, requiring explicit mapping of mploy stage names to Crelate pipeline stage values during the configuration phase before import begins.

mploy Pipelines define the ordered sequence of stages a Candidate moves through (e.g., Applied, Phone Screen, Interview, Offer). We preserve the ordered stage sequence as a Crelate Pipeline with corresponding stage values. Stage names and counts vary by customer configuration in mploy; we enumerate the full stage list during discovery and configure matching stages in Crelate before any Application records are imported.

Interview records, including interviewer assignments, scores, and feedback, are not confirmed as a separately exportable object in mploy. Where interview data exists, we capture it from the candidate record's notes or activity log and import it as a Crelate Note attached to the relevant Candidate record. The note body includes interviewer name, date, and feedback summary in structured text format.

Offer records contain compensation details, start dates, and acceptance status. These are linked to Applications in mploy and map to Crelate's Offer object with compensation fields, start date, and offer status. We preserve the Offer-Application relationship by resolving the parent Application reference during import. Offer status values (pending, accepted, declined, retracted) map to equivalent Crelate status values.

User accounts in mploy represent employees with access to the ATS. Role assignments (admin, recruiter, hiring manager) map to Crelate's role model. Inactive users may be excluded or preserved as inactive records depending on the customer's preference. We resolve users by email match where possible and flag any users that cannot be matched for manual reconciliation before import.

Custom fields on Candidates require explicit enumeration during scoping because mploy has no published data dictionary. The customer provides screenshots or an export of their field configuration, and we create matching custom fields in Crelate with appropriate data types (text, number, picklist, date, checkbox). Custom field values migrate as part of the Candidate export. We validate field types and picklist values against Crelate's schema before the production import batch runs.

Custom fields on Jobs in mploy follow the same enumeration process as Candidate custom fields. We enumerate field names, data types, and picklist values during discovery and create matching custom fields in Crelate before Job import. If mploy allows custom fields on Jobs in the customer's specific configuration, we confirm this during the initial scoping call and adjust the export request accordingly.

Resume files and uploaded attachments in mploy are stored separately from candidate record fields. If mploy stores attachments outside the candidate CSV export, we request a separate file archive or confirm that attachment export is included in the bulk download. Missing attachments are a common post-migration gap when scoping focuses on record fields and ignores binary assets. We map each file to a Crelate Candidate record using email or name matching.

If mploy exposes any activity history (notes, calls, emails) in the admin-panel export, we map these to Crelate Activities linked to the relevant Candidate or Job record. The mapping depends on what fields are available in the export; if only free-text notes are available, these migrate as Crelate Notes. Structured activity types migrate to Crelate's Activity record types where supported.

Effective-dated hiring pipeline stage transitions are preserved by capturing the timestamp when each Application moved to a given stage in mploy. We replay these timestamps as stage entry dates in Crelate's pipeline history, maintaining the chronological record of a candidate's progression through the hiring process for audit and reporting purposes.