Migrate from LogicMelon to Crelate

LogicMelon Job records map directly to Crelate Job. The job title, description, location, employment type, salary range, and posting schedule migrate as typed fields on the Crelate Job. We preserve the original LogicMelon job board target list as a comma-separated tag on the Crelate Job labeled 'Original Board Distribution' so teams can see which boards originally received each advert without re-executing the multi-post. The job's posting status (draft, active, paused, closed) maps to Crelate's job_status field.

LogicMelon Application records contain both candidate profile data and application metadata. We split each Application into a Crelate Contact (the candidate person record) and a Crelate Application (the submission record). Contact fields include name, email, phone, address, work history, skills, and desired salary sourced from LogicMelon's structured profile. The original LogicMelon Application ID is preserved in a custom field on the Crelate Contact as a migration reference key.

The application-side of the split maps to Crelate's Application record linked to the corresponding Job and Contact. The original application status (Applied, Screened, Interviewed, Offered, Placed, Rejected) maps to Crelate's application status field, and any LogicMelon screening notes, scores, or rating fields migrate to custom fields on the Crelate Application record. The application date and last-modified date migrate as typed date fields for timeline accuracy.

LogicMelon Candidate profiles include structured fields (name, email, phone, work history, skills, education) plus a CV file attachment. We migrate the structured fields directly to Crelate Contact fields and extract the CV document (PDF or Word) as a file attachment linked to the Contact. Any candidate data already captured in LogicMelon's structured profile fields takes priority; the CV file serves as the source-of-truth backup for records where structured fields are incomplete.

Recruiter notes and screening scores attached to LogicMelon Applications are migrated as notes on the Crelate Application record. Where LogicMelon uses structured rating fields (numeric scores or stage-based evaluations), we map these to Crelate custom fields on the Application object so they are searchable and reportable post-migration.

LogicMelon's configurable pipeline stages (Applied, Screened, Interviewed, Offered, etc.) are mapped to Crelate's Application Status picklist values during migration. We identify the customer's active stage names during discovery and configure matching status values in Crelate before the Application import phase, flagging any stages that do not have a direct Crelate equivalent for admin decision.

LogicMelon stores the list of targeted job boards per job advert rather than as a global posting template. We preserve this board-association list as a tag on the Crelate Job record. Each board name in the original list becomes a separate tag so teams can filter jobs by original distribution channel. The tag is informational; Crelate's native job distribution (including its LogicMelon integration) handles ongoing posting rather than replicating the original board list directly.

LogicMelon Users tied to Applications and Jobs are mapped by email to Crelate User records. We export the user assignment on each record during extraction and resolve by email against the destination Crelate tenant's User table during import. Users without a matching Crelate User are placed in a reconciliation queue for the customer's admin to provision before the final import phase.

LogicMelon's multi-tenant organisation hierarchy (agency-level vs. client-level structures) is mapped to Crelate's Organisation or Company objects depending on whether the structure represents the recruiting agency itself or client organisations. We extract the hierarchy during discovery and configure the appropriate Crelate data model before data import.

LogicMelon custom fields on Job records are identified during discovery and mapped to Crelate Job custom fields. We create the destination custom field in Crelate (with matching field type where possible: text, number, picklist, date) before the Job import phase. Fields with value types that Crelate does not support are flagged for admin decision on fallback handling.

LogicMelon custom fields on Application records are mapped to Crelate Application custom fields. Like Job custom fields, destination fields are pre-created during the schema phase with equivalent types. Multi-select picklists in LogicMelon map to Crelate multi-select picklists or text fields depending on Crelate's field-type availability at the customer's plan tier.

File attachments beyond CVs—supporting documents attached to Jobs or Applications in LogicMelon—are extracted from the file store and reattached to the corresponding Crelate record. We identify attachment types during discovery and route them to the correct parent record (Job or Application) based on the original attachment context in LogicMelon.