Migrate from RESUMate to Recruit CRM & ATS

RESUMate Candidates map directly to Recruit CRM Contacts. We extract all structured fields from the CSV export (name, email, phone, address, parsed resume text) and load via Recruit CRM's Contacts API. Email address is the primary dedupe key; candidates with duplicate emails are flagged to the customer for resolution before insert. Parsed resume text populates the Contact profile summary field, and original resume file attachments load as binary uploads via Recruit CRM's document attachment endpoint.

RESUMate Clients map to Recruit CRM Companies. The Client name, contact person, industry, and billing address fields transfer directly. Company name is the dedupe key for import. We resolve any Client records that have no associated Job Orders by flagging them for the customer to confirm active status before insert to avoid populating Recruit CRM with dormant client records.

RESUMate Job Orders map to Recruit CRM Jobs. We extract job title, job description, requirements, location, salary range, and status from the CSV export. The Job status (Active, On Hold, Filled, Cancelled) maps to Recruit CRM's job_status field. Each Job Order is linked to a Client record (mapped Company) at import time using the RESUMate Client-to-Job relationship preserved during extraction.

RESUMate Send-outs track Candidate submissions to Job Orders. We extract send-out records as a separate table during export, then create Recruit CRM Application records (one per candidate-to-job pairing). The Application links the mapped Contact (Candidate) to the mapped Job (Job Order). Send-out date, status, and notes transfer to the Application record, preserving the submission history that drives placement reporting.

RESUMate Groups segment Candidates, Clients, or Job Orders into named lists. We extract group membership as a tag table during export, then import tags into Recruit CRM's tag system. Each Group name becomes a Tag; membership records create TagAssignment links to the corresponding Contact, Company, or Job. The customer confirms during scoping whether all Groups should migrate as tags or whether inactive or abandoned Groups should be excluded.

RESUMate Active Jobs are filtered views of Job Orders organized by pipeline stage and status. These are derived records, not a separate object. We extract the active Job Order records and their current pipeline stage, then configure Recruit CRM's job pipeline with stages that mirror the customer's active job statuses. Stage names and order are confirmed during scoping against Recruit CRM's pipeline configuration options.

RESUMate deployments commonly accumulate hundreds of custom fields over years of use. We audit the full custom field schema during discovery, identifying fields that contain live data versus fields that are defined but empty. We create equivalent custom fields in Recruit CRM during the schema-design phase (deployed to a sandbox first), then map only the fields with populated data during import. Type mismatches (date vs. text, picklist vs. free text) are resolved through transform scripts at migration time.

RESUMate stores resumes as proprietary-format files alongside parsed CSV text. We extract the original binary files from the export, convert them to standard Word or PDF formats where the RESUMate format permits, then upload each file to the corresponding Contact record in Recruit CRM via the API attachment endpoint. Parsed resume text also populates the Contact profile to ensure the data is searchable even if the attachment fails or is unsupported.

RESUMate Notes on Candidates are free-text rows with timestamps. We export notes as a dedicated table and import them into Recruit CRM as Activity Log entries (or as Notes attached to the Contact). Each activity record preserves the note body, creation date, and the RESUMate user who created it (mapped to a Recruit CRM user by email match). Notes without a date are assigned the import date and flagged for the customer's review.

RESUMate Calendar events are linked records tied to Candidates, Clients, or Job Orders. We extract event type, date, duration, and notes from the Calendar export. Events with a defined duration map to Recruit CRM Meetings; single-point-in-time events (interviews, calls) map to Tasks with a due date. All events link to the parent Contact and Job record using the lookup relationships created during the parent-record resolution phase.

RESUMate does not have a formal user management object equivalent to Recruit CRM's User model. We extract owner references from Candidate, Client, and Job Order records and match them to Recruit CRM users by email during import. Owners without a matching Recruit CRM user account are placed in a reconciliation queue for the customer's admin to provision before record import resumes.