Migrate from RESUMate to Crelate

RESUMate Candidate records map directly to Crelate Contact. The parsed resume text maps to Crelate's contact profile fields; phone, email, address, and current employer transfer as standard fields. We map the source candidate's status (Active, Placed, Passive) to Crelate's contact status enumeration. Any RESUMate custom fields on the Candidate record are pre-created in Crelate as custom contact fields before migration and populated during the bulk load.

RESUMate Client records map to Crelate Company. Client name, address, industry classification, and any client-specific notes transfer as standard Company fields. We extract the Client record as the first phase of migration so that the Company ID is available for resolving the Candidate-to-Client relationship when Contacts are loaded in the second phase.

RESUMate Job Order records map to Crelate Job. Job title, description, requirements, status (Open, Filled, Closed, On Hold), and assigned recruiter transfer as standard Job fields. The Job-to-Client link from RESUMate maps to the Job's Company association in Crelate. We load Jobs after Companies but before Candidates to satisfy the parent-record lookup constraint.

RESUMate Send-outs — which track when a Candidate is submitted to a Job Order — map to Crelate Candidate Submission records or the equivalent activity type in the Crelate Job pipeline. We reconstruct the send-out as a submission event with the candidate, job, date, and submission status (Sent, Interview, Offer, Placement) preserved. If Crelate does not have a standalone submission object at the customer's tier, we map send-out data to an activity note on the Contact tied to the Job.

RESUMate Active Jobs are filtered views of Job Orders organized by pipeline stage and status. These are derived views, not separate records. We extract the active pipeline stage assignment from Active Jobs and apply it as a Job status field in Crelate. The customer's specific pipeline stage labels (for example: Sourced, Screened, Interviewing, Offered, Placed) are mapped to Crelate's Job status enumeration during configuration.

RESUMate Groups are named segmentation lists that organize Candidates, Clients, or Job Orders. We extract Group membership as a tag-keyed export and create corresponding Tags in Crelate. The tag is applied to the matching Contact, Company, or Job record during bulk load. We configure tag creation before migration so that the tag vocabulary is available at import time.

RESUMate Notes on Candidates, Clients, and Job Orders transfer as Activity Note records in Crelate's contact and company timeline. Each note carries the original timestamp, author (recruiter name), and note body. We link the activity note to the correct Contact or Company by resolving the RESUMate record ID to the migrated Crelate ID during the transform phase.

RESUMate Calendar events linked to Candidates, Clients, or Job Orders transfer as Crelate Event records. Event type (interview, client call, internal meeting), date, time, and notes are preserved. We resolve the event's parent record reference at migration time and link the Event to the migrated Contact or Job in Crelate.

Original resume files from RESUMate (Word, PDF, plain text) are extracted as binary blobs and uploaded to Crelate as Contact resume documents linked to the matching Candidate Contact. We handle the file upload in Crelate's document attachment API after the Contact record is created and verified. If the RESUMate database stores resume files in a proprietary or encrypted format, we work with the customer during discovery to confirm file exportability.

RESUMate's unlimited custom field capability means the actual field schema is installation-specific. We discover the full candidate custom field schema during discovery, pre-create matching custom fields in Crelate's contact object before migration, and handle any data type translation (date fields, picklist values, free text) during the transform phase. RESUMate custom fields capturing industry-specific candidate data points are preserved as-is or normalized if the destination field type differs.

RESUMate job orders frequently carry custom fields for industry-specific job requirements, compensation ranges, or sourcing notes. We discover the job custom field schema during discovery, pre-create matching custom fields in Crelate's Job object, and map values during the Job phase of migration. Custom fields that reference other RESUMate records (for example, a Preferred Client custom field) are resolved to the migrated Crelate ID before insert.

RESUMate Owner records (assigned recruiters) map to Crelate User records by email match. We extract all distinct owner IDs from Candidate, Client, and Job Order records and resolve them against the destination Crelate user list. Any RESUMate owner without a matching Crelate user is flagged in a reconciliation report for the customer's admin to provision before record import resumes, since OwnerId is required on most standard record types.