Migrate from mploy to Recruit CRM & ATS

mploy Candidates map directly to Recruit CRM Candidates. Standard fields (name, email, phone, status, source, submission date) migrate via CSV with direct field-to-field mapping. Resume files require a separate attachment export step from mploy; we deliver them as file attachments linked to the corresponding Candidate record in Recruit CRM after bulk import completes.

mploy Job records (title, department, location, description, status, open/closed flag) map to Recruit CRM Jobs. We preserve active and archived job status, mapping mploy's open/closed state to Recruit CRM's job status field. Job-associated custom fields migrate to Recruit CRM custom fields on the Job object, respecting the plan limit (15 on Pro, 100 on Business).

mploy Applications (the join record between Candidate and Job) map to Recruit CRM Applications. The mapping preserves submission date, application source, current stage, and any stage-transition timestamps. Stage names from mploy's pipeline configuration map to Recruit CRM's pipeline stages during import.

mploy pipeline stage names and sequence order are customer-specific. We extract the ordered stage list during discovery, then configure Recruit CRM pipeline stages to match before application records are imported. Stage probability values from mploy (if present) migrate as stage-level notes in Recruit CRM.

mploy User accounts (recruiters, hiring managers, admins) map to Recruit CRM users by email. Role assignments (admin, recruiter, viewer) map to Recruit CRM permission roles during user provisioning. Inactive mploy users may be excluded or migrated as inactive Recruit CRM users depending on whether historical assignment data needs to be preserved.

mploy Offer records (compensation, start date, acceptance status) map to Recruit CRM Deals linked to the corresponding Application and Job. We preserve offer amount, start date, and status fields. If mploy does not have a distinct Offer object, offer data stored as custom fields on Applications migrates as Deal fields in Recruit CRM.

mploy interview records are not confirmed as a separately exportable object. Where interview data exists in mploy (interviewer name, date, outcome notes), we capture it as notes attached to the Application record in Recruit CRM. Recruit CRM's native interview scheduling feature is available post-migration but historical interview records do not map to a native interview object through CSV import.

mploy custom fields on Candidates must be explicitly enumerated by the customer during discovery because no public data dictionary exists. Each custom field name, data type, and picklist value is captured manually. On Recruit CRM's Pro Plan, up to 15 custom fields per object are supported; the Business Plan supports up to 100. If the customer exceeds Pro limits, we flag the constraint during scoping and recommend Business Plan or field consolidation before migration.

Same enumeration constraint applies to mploy custom fields on Jobs. Recruit CRM supports job-specific custom fields including job-associated fields (custom fields scoped to specific job roles a candidate is being considered for). We map mploy job custom fields to Recruit CRM job custom fields, using the job_associated_fields structure where applicable to preserve role-specific data context.

Application source attribution (e.g., LinkedIn, job board, referral) from mploy migrates to Recruit CRM's candidate source field. If mploy stores source as a free-text field, we standardize it to Recruit CRM's picklist values during transform. Unknown or unmapped source values are preserved in a custom field for the customer's admin to reclassify post-migration.

Resume files and uploaded attachments stored outside the candidate CSV in mploy require a separate file archive export. We link each file to the corresponding Candidate record in Recruit CRM by filename matching against the candidate email or name in the primary export. This step is manual and requires the customer to confirm that the admin-panel bulk download includes attachments or that a separate archive can be generated.

Any notes recorded on mploy Candidate or Application records migrate as Recruit CRM Notes attached to the corresponding record. Timestamps and author information are preserved where present. If mploy stores engagement activity (emails, calls) as a separate object, those migrate as Note records; native Recruit CRM email and call logging features are available post-migration for ongoing activity capture.