Migrate from Journeyfront to Crelate

Journeyfront Jobs map to Crelate Job records. We extract job title, description, location, department, employment type, and job board posting status. Journeyfront's job board posting flags migrate to Crelate's distribution settings. The Job record is the primary parent for all candidate sub-records and must be created before any candidate migration so that the job lookup is satisfied.

Journeyfront Candidates map to Crelate Person records. The full candidate profile — contact information, work history, screening responses, and pipeline stage assignment — migrates as structured fields. We preserve the candidate's original Journeyfront record ID in a custom field for audit traceability. Any candidate without a matching email in Crelate is inserted as a new Person record; duplicates are resolved by email dedupe.

Journeyfront assessment scores migrate as custom numeric fields on the Crelate Person record. We map each distinct Journeyfront assessment dimension (retention prediction, performance score, screening composite) to a corresponding custom field in Crelate. The company-specific calibration algorithm does not export — this is a documented gap. We flag all assessment records during scoping so the customer's admin can establish new baseline scoring in Crelate or decide which assessment dimensions to retain as historical reference data.

Journeyfront screening question responses (common in BPO multi-client contexts) migrate to Crelate custom candidate fields. Question text and scoring rubrics extract as metadata and map to Crelate's question library where the destination supports it. BPO clients with client-customized screening recipes will need to rebuild these in Crelate's job-specific screening configuration post-migration.

Journeyfront's custom pipeline stages per job or workflow map to Crelate's stage framework. Stage names, order, and any time-based triggers export from Journeyfront and are remapped to the nearest Crelate stage equivalents. Crelate's drag-and-drop pipeline builder accepts these as starting configuration, but stage automation rules (time delays, score thresholds) are documented separately and require rebuild in Crelate's workflow builder post-migration.

Journeyfront interview records — including interviewer assignment, scheduled date and time, scorecards, ratings, and overall recommendation — migrate to Crelate Activity records of type Interview. We preserve the interviewer lookup by email match against Crelate's user directory and link the activity to the candidate's Person record. Notes attached to the interview migrate as activity notes.

Journeyfront Offer records map to Crelate Offer records. We extract position reference, compensation details (salary, bonus, equity if present), offer status, and candidate response. Status values (pending, accepted, declined, withdrawn) remap to Crelate's offer status taxonomy. The offer record links to the candidate's Person record and the related Job record.

Journeyfront users, hiring managers, and interviewers map to Crelate User records by email resolution. Role assignments (hiring manager, recruiter, interviewer, coordinator) migrate to Crelate's permission-based roles. Any Journeyfront user without a matching Crelate User account enters a reconciliation queue for the customer's admin to provision before candidate migration begins.

Journeyfront automation rules (triggers based on stage, score thresholds, or time delays) are extracted as rule definitions and translated to a written inventory. Crelate's workflow builder is different from Journeyfront's trigger model. We do not migrate automation rules as code. The inventory document lists every active Journeyfront automation with its trigger logic, conditions, actions, and the recommended Crelate equivalent for the customer's admin to rebuild.

Journeyfront's analytics dashboards (turnover reduction, tenure improvement, SLA metrics) are computed dynamically from raw data and have no flat export. We recommend exporting PDF snapshots of key reports before migration cutoff. All underlying candidate, assessment, and interview data migrates normally, so Crelate's reporting tools can generate equivalent metrics post-migration from the migrated dataset.

Journeyfront integrations with job boards, background check vendors, and HRIS systems are configured via API credentials in the Journeyfront platform. These credentials are external to the data export and do not migrate. Job board posting integrations, background check connections, and HRIS sync settings must be reconfigured manually in Crelate. We provide a list of all active Journeyfront integrations as a reference for the customer's admin during Crelate configuration.

If Journeyfront contains company-linked candidate data (common in BPO or professional staffing contexts), Journeyfront Company records map to Crelate Organization or Client records. The mapping depends on whether the company represents a client (staffing agency) or a hiring company (corporate). We clarify the intended mapping during scoping and configure Crelate's organization type accordingly.