Migrate from Easy Tech to Crelate

Easy Tech candidate records map to Crelate Contacts. The Contact record becomes the primary candidate profile in Crelate's ATS+CRM model. Original create date and last-modified timestamp are preserved as custom fields since Crelate's native CreatedDate reflects the migration timestamp rather than the original Easy Tech record creation date. This preservation ensures historical reporting continuity for time-in-pipeline and candidate aging analyses.

Resume files attached to Easy Tech candidate records are re-uploaded to Crelate as Contact attachments. File size limits apply — Crelate handles documents up to 25MB per file. Multiple resume versions in Easy Tech are consolidated to the most recent version plus a historical versions attachment.

Easy Tech skill tags stored as a comma-separated list or tag field are transformed into a Crelate multi-select custom field on Contact. If Easy Tech stores skills as individual related records, they are concatenated into a single multi-select value within Crelate's field constraints.

Easy Tech client corporation records map directly to Crelate Companies. Company name, address, industry, website, and revenue fields map to their Crelate equivalents. Parent-child company hierarchies in Easy Tech translate to Crelate's Company ParentId relationship. Multi-level hierarchies are flattened where necessary to maintain referential integrity during migration.

Easy Tech job orders map to Crelate Jobs. Job title, description, requirements, status, and assigned recruiter map to Crelate Job fields. Job status pick-list values are mapped value-by-value to Crelate's Job status pick-list — active, filled, closed, on-hold, and cancelled statuses require explicit value mapping.

Easy Tech candidate-to-job submissions map to Crelate's candidate status on Job records. Submission date, current status, and source (direct, referral, job board) are preserved as fields on the Job's candidate list. Status values are mapped to Crelate's candidate status pick-list per job pipeline.

Easy Tech placement records (accepted offers, hired candidates) map to Crelate's Placements object. Placement links the Candidate (Contact) to the Job and captures fee percentage, pay rate, start date, salary, and client billing details. Placements in Easy Tech without a structured object are reconstructed from job order status changes and candidate activity history.

Easy Tech call logs, email logs, and notes attached to candidates or jobs map to Crelate Activities. Activity type, subject, body, date, and owner are preserved. Each activity links to its parent Contact or Job record. Original timestamps are kept; Crelate's activity date reflects the original Easy Tech activity date.

Easy Tech recruiter and user assignments resolve by email match against Crelate Users. Unmatched owners are flagged before migration — either the user is provisioned in Crelate first or their records are assigned to a fallback Crelate user during migration. System admin must verify user provisioning before migration runs.

Easy Tech custom candidate fields exceeding Crelate's 20-field cap per entity require compression. Our team audits active versus deprecated fields, merges related fields where values permit, and archives fields with no data. Remaining active fields are created as Crelate Contact custom fields before migration loads data.

Easy Tech custom job order fields map to Crelate Job custom fields. Job-specific fields like salary range, remote policy, security clearance requirements, or client budget notes are evaluated for Crelate field type compatibility. Multi-select job field values are mapped to Crelate pick-lists with explicit value mapping configuration.

Easy Tech pipeline stages (sourcing, screening, interviewing, offer, etc.) map to Crelate Job status values. If Easy Tech uses multiple pipelines with different stage sets, each pipeline maps to a separate job status value set in Crelate — this requires explicit value mapping per stage name in each pipeline.