Migrate from eArcu to Crelate

eArcu Candidate records carrying name, contact details, work history, and ta scores map directly to Crelate Contact. We extract all standard fields (first_name, last_name, email, phone, address, current_title, current_company) and map any custom profile properties to Crelate custom fields under Core Records > Contacts. During discovery we confirm whether the source schema is legacy eArcu or PageUp unified, because field naming conventions differ. Assessment scores stored as linked candidate records migrate to custom number or text fields on the Contact. The candidate deduplication key is email address.

eArcu Requisitions including title, department, location, employment type, and pipeline assignment map to Crelate Jobs. We map requisition metadata and preserve any custom approval workflow configurations by documenting them as a configuration reference for Crelate's admin to rebuild. Job status (open, filled, cancelled) maps directly. The primary eArcu hiring manager on the requisition becomes the Crelate Job Owner.

eArcu Application records link a Candidate to a Requisition with timestamps for each stage transition. These map directly to Crelate's Application object. We preserve the full stage history per application including stage-entry dates, which we translate to the Crelate pipeline's stage model. Application source (direct, referral, job board) migrates as a custom field if not a native Crelate field.

eArcu supports configurable pipeline stages per requisition. We extract the full stage history per application and map each eArcu stage name to a corresponding Crelate pipeline stage. Stage-entry dates and stage-transition timestamps are preserved as activity date fields on the Crelate Application record. Crelate pipeline stages are configured under Settings > Pipelines > Stages before application data loads.

Cognitive test results, personality questionnaire scores, and situational judgement data are stored as linked records in eArcu. Crelate has no native assessment object, so we export raw scores and assessment types as a separate dataset and map them to custom number or picklist fields on the Crelate Contact record. We coordinate with the customer during scoping to define the exact field names, types, and picklist values that match their reporting needs. Assessment metadata (test date, test type, provider) migrates as additional custom fields.

CVs, cover letters, and supporting files attached to candidates or applications are binary blobs stored in eArcu's document store. We extract the files and re-upload them to Crelate, preserving original filenames and attaching them to the correct Contact or Application record. We flag any files that cannot be linked to a valid parent record for manual resolution. File type, size, and upload date are preserved in Crelate's attachment metadata.

eArcu User accounts, roles, and permissions define who can view or act on requisitions and candidates. We export the user roster with role assignments and map to Crelate's permission model. User provisioning in Crelate requires the customer's admin to create the User records (since Crelate manages user lifecycle natively). We provide a user mapping spreadsheet with email, name, role, and the corresponding Crelate permission set. Any eArcu user without a Crelate counterpart goes to a reconciliation queue for the admin to resolve.

eArcu Offer records include compensation details, start dates, and approval status. Where Crelate has a dedicated offer module (Business Plus tier), we map fields directly. In the absence of a dedicated offer object, we attach offer data as custom properties on the Job or Application record. Compensation amount, currency, start date, and approval status migrate as text or date custom fields. We confirm the offer model with the customer during discovery.

Career portal pages, job board widgets, and branding assets in eArcu are HTML and CSS configurations rather than structured database records. These do not migrate as transferable assets. We export the content export package where available, document the page structure and any active job board widget configurations, and deliver a rebuild guide for Crelate's portal builder and Custom CSS settings. The customer recreates career site content in Crelate using the document as a blueprint.

Animated onboarding packages and structured onboarding task sequences are platform-native eArcu configurations that cannot be meaningfully transferred to Crelate. We do not migrate them as records. We document the existing package structure — task sequence, responsible parties, document checklists, and timeline — as a detailed rebuild guide that the customer's admin uses to configure equivalent onboarding steps in Crelate or a separate onboarding tool. This guide is delivered as part of the standard migration package.

eArcu custom fields layered on the Candidate object (beyond standard name, email, phone) require pre-configuration in Crelate before migration. We extract the full custom field schema during discovery — field name, type (text, number, date, picklist, checkbox), and any validation rules — and pre-create these as Crelate Core Record custom fields under Settings > Core Records > Contacts. Field type mapping follows Crelate's supported types: text fields map to Text, numeric scores to Numbers (Integer or Decimal), date fields to Date, and picklist values to Picklist with the options migrated as Crelate picklist values.

eArcu records every stage transition on an Application with a timestamp and optional note. We extract this history and load it into Crelate's Application activity timeline using Crelate's API or activity import tools. Each stage transition appears as a timestamped activity entry with the stage name and any associated notes. This preserves the full candidate progression audit trail that recruiters rely on during compliance reviews and placement audits.