Migrate from Nextal to Crelate

Nextal Job postings map to Crelate Job records with Name, description, department, location, and status preserved. Nextal Jobs can carry multilingual content which we store as separate custom text fields (e.g., description_fr, description_es) in Crelate if the destination org has multilingual requirements configured. Job status in Nextal (Active, Paused, Closed) maps to Crelate Job Status values. We extract Jobs first to establish the Job IDs used as foreign keys in the Application mapping phase.

Nextal Candidate profiles map to Crelate Contact records. Name, email, phone, and address fields migrate directly. Resume attachments are downloaded from Nextal and uploaded to Crelate as document attachments on the Contact record. Source attribution (LinkedIn, Indeed, direct application) stored in a custom field in Nextal maps to Crelate's candidate source tracking. Candidate records are extracted before Applications so that Contact IDs are available for the Application-to-Contact linkage during import.

Nextal Applications link a Candidate to a Job and carry stage history. In Crelate, a Contact can be associated with a Job through a Job Submission (an activity-type record) or through a separate Opportunity record depending on the agency's workflow. We create Crelate Job Submissions linked to the Contact and the target Job record. Pipeline Stage assignments from Nextal are preserved as custom fields on the Job Submission. A single Candidate applying to multiple Jobs in Nextal results in multiple Job Submissions in Crelate.

Nextal's Kanban-style Pipeline Stages are configurable per organization. Stage names and ordering vary by team, requiring a customer-reviewed stage mapping table before migration. We extract the full stage list from Nextal, present it alongside Crelate's Job Status picklist values, and the customer determines the mapping. Stage probability percentages (if stored in Nextal) migrate to custom numeric fields on the Job Submission record. The mapping is validated in a test pass before production migration.

Nextal User accounts (recruiters, hiring managers, admins) migrate to Crelate User records with names, email addresses, and role assignments preserved. Passwords do not transfer; users receive Crelate setup emails upon provisioning. We match by email address. Any Nextal Owner referenced on a record without a corresponding Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Nextal custom fields on Job postings require field-level mapping. We extract the field schema (label, data type, picklist values), match by label and data type to Crelate custom fields on Job, and create any unmapped custom fields in Crelate before the Job import phase. Data types are reconciled: Nextal text fields map to Crelate Short/Long Answer, numeric fields to Crelate Number (Integer or Decimal), and picklist fields to Crelate Picklist.

Nextal custom fields on Candidate records map to Crelate custom fields on Contact records. We apply the same field schema extraction, type reconciliation, and pre-creation process used for Jobs. If Nextal stores candidate clearance levels or clearance expiration dates as custom fields, these map to Crelate custom fields on Contact with appropriate data types. The mapping is reviewed with the customer before migration to ensure picklist values align.

Resume and document attachments on Nextal Candidate records are downloaded, mapped by candidate email to the corresponding Crelate Contact, and uploaded as downloadable documents. File format is preserved; PDF and DOCX are the primary formats supported across both platforms. We log the original file name, upload date, and source (resume, cover letter, portfolio) as metadata. Attachment volume affects migration timeline and price when exceeding 10,000 files.

Nextal stores multilingual email templates tied to job stages as HTML blobs. We extract templates as HTML with any merge field syntax preserved as plain text notes. Each language variant is imported as a separate Crelate Email Template, tagged by language. Templates are reviewed in a Crelate test environment before production import. HTML rendering is validated across Crelate's email client compatibility settings.

If Nextal stores employer or client company records separately from Job postings (some agency configurations do), those map to Crelate Company records. Company Name, website, industry, and address fields migrate directly. The Company-to-Contact linkage is established through Crelate's Company lookup on the Contact record after both objects are imported.

Nextal candidate notes and activity history migrate to Crelate Activity records linked to the Contact. Note body, timestamp, and author (User) migrate directly. We resolve the Nextal User reference to the corresponding Crelate User by email match. Activity ordering is preserved by setting the Activity date to the original Nextal timestamp.

Recruiter tasks and follow-up items stored in Nextal migrate to Crelate Task records attached to the Contact or Job. Task status, priority, due date, and body text migrate directly. Assignment resolves the Nextal Owner to the Crelate User by email. Tasks without an assignable Crelate User are set to the migrating admin's account with a note to reassign.