Migrate from LogicMelon to Recruit CRM & ATS

LogicMelon Job records map to Recruit CRM Job records. The job advert content (title, description, requirements, location, salary) migrates directly to Recruit CRM's Job fields. The original LogicMelon job reference ID is preserved in a custom field for audit and cross-system reconciliation. The per-job board target list from LogicMelon is not replicated as a multi-posting action in Recruit CRM (Recruit CRM uses XML feed distribution configured at the account level), but the list of originally targeted boards is saved as a tag field on the Job record so teams can see the original posting distribution. We extract the board list during the discovery phase and build it as a comma-separated tag string in Recruit CRM during import.

LogicMelon Candidate profiles map to Recruit CRM Candidates. Structured fields (name, email, phone, location, skills, work history) migrate directly. Any CV document stored as a binary attachment in LogicMelon is extracted as a PDF or DOCX file and attached to the Recruit CRM Candidate record via the Recruit CRM Files API (POST /v1/files) with the attachment linked to the candidate_id. The original CV filename is preserved. Candidate status history from LogicMelon's pipeline stages migrates as a custom text field or as a note entry with the stage name and timestamp, depending on the customer's Recruit CRM plan configuration.

LogicMelon Application records — which represent a Candidate's response to a specific Job — map to Recruit CRM Application records. The mapping resolves the parent Candidate (by email or candidate_id) and parent Job (by original LogicMelon job reference) at migration time using lookup tables built during the discovery phase. Application status from LogicMelon (e.g. Applied, Screened, Interviewed, Offered) migrates to the Recruit CRM application stage, and any screening score fields are mapped to custom fields on the Application record.

LogicMelon CV documents are binary attachments linked to Candidate records. We extract the raw file (PDF or Word format) from LogicMelon's file store and upload it to Recruit CRM using the Files endpoint (POST /v1/files with candidate_id in the association). If multiple CVs are attached to a single LogicMelon Candidate (e.g. different versions or formats), all versions are uploaded with descriptive filenames (original_filename_v1.pdf, original_filename_v2.pdf) to preserve the complete record. The migration of CVs adds meaningful overhead because each file requires a separate API call to Recruit CRM, which is factored into the timeline estimate for large-volume migrations.

Recruiter notes and screening scores attached to LogicMelon Applications are extracted as structured text and mapped to Recruit CRM Notes (via POST /v1/notes) linked to the Application record, or to custom fields on the Application if the screening data follows a consistent scoring format. During discovery, we identify whether the customer's LogicMelon instance uses free-text notes, structured rating scales, or a combination, and configure the mapping accordingly before migration begins.

LogicMelon pipeline stages are configurable per customer (Applied, Screened, Interviewed, Offered, Hired, Rejected, etc.). We extract the customer's active stage names during discovery and map them to equivalent Recruit CRM application stages. If the destination Recruit CRM instance uses different stage names, we configure the stage mapping in a custom field first so that status history is preserved accurately rather than defaulting to an arbitrary stage that loses meaning.

LogicMelon stores the list of job boards targeted per job advert as a board-association object rather than a global template. During migration, we extract each job's board list and create Recruit CRM tags for each board name (Indeed, LinkedIn, Reed, etc.). The tags are associated with the Job record. This preserves the original distribution footprint for audit and reference, but it does not recreate the multi-posting action itself — Recruit CRM distributes jobs through XML feed configuration in its job board settings, which is a separate configuration step the customer's admin handles post-migration.

LogicMelon's multi-tenant hierarchy (agency-level vs. client-level or sub-unit structures) requires a structural decision in Recruit CRM. If the agency operates multiple client desks or brands, we map the LogicMelon sub-unit hierarchy to Recruit CRM Companies (for client-facing structures) or to Recruit CRM Teams (if the destination instance has Team features enabled on the plan). We make this call during discovery based on the customer's intended Recruit CRM plan configuration.

LogicMelon users tied to the organisation via API credentials are mapped to Recruit CRM users by email match. We extract the hubspot_owner_id or recruiter assignment from LogicMelon Jobs and Applications and match against the Recruit CRM user table during import. Any LogicMelon user without a matching Recruit CRM user is flagged in the reconciliation report for the customer to provision before record assignment migrates. Active vs. inactive status on the Recruit CRM side is determined by whether the original recruiter is still engaged with the team.

LogicMelon allows custom fields on Jobs and Applications. During discovery, we identify all active custom fields and their data types (text, number, date, picklist, checkbox). We pre-create equivalent custom fields in Recruit CRM before migration begins using the Recruit CRM custom fields API (POST /v1/custom-fields). Type mismatches (e.g. a LogicMelon free-text custom field that should map to a Recruit CRM picklist) are resolved by the customer's admin during the scoping phase to avoid silent data truncation.