Migrate from Nextal to BambooHR

Nextal Job postings map to BambooHR Job records. We extract job title, description, department, location, employment status, and job posting URL. Multilingual job content is mapped to BambooHR's language-specific job posting fields or stored as custom fields if the destination is configured for multiple locales. The Nextal Career Portal URL is preserved as a reference in a BambooHR custom field for audit. Job status (open, closed, draft) maps directly to BambooHR active/inactive status.

Nextal Candidate profiles map to BambooHR Employee records. We extract first name, last name, email address, phone number, current title, source attribution (LinkedIn, Indeed, direct application), resume attachment URL, and any candidate custom fields. The candidate source field becomes a BambooHR custom field because BambooHR's standard Employee model does not include an ATS-style source attribution field. If the candidate has been hired, we create an active Employee record; otherwise, candidate records remain in BambooHR's Job Application module as applicants.

Nextal Application records link a Candidate to a Job and carry stage history. We map Applications to BambooHR Job Applications, preserving the Kanban stage assignment as a custom field or structured note attached to the Job Application record. Nextal stage names are not natively supported in BambooHR's standard application model, so we either create BambooHR custom stage fields or attach a structured note with the original Nextal pipeline stage and transition dates for audit continuity.

Nextal's Kanban-style pipeline stages (configurable per organization) require a configuration step before migration. We extract the full Nextal stage list including stage order, stage names, and any custom stage flags, then map them to BambooHR job stages using a customer-reviewed stage mapping table. If BambooHR's default stage set (Applied, Phone Screen, Interview, Offer, Hired, Rejected) does not cover the customer's pipeline, we create custom job stages in BambooHR's admin settings before importing application records.

Nextal User accounts (recruiters, hiring managers, admins) migrate to BambooHR Employee records with User access. We extract name, email address, and role assignment. We do not transfer passwords; Users receive BambooHR setup emails at their migrated email address. Any Nextal user who does not have a corresponding BambooHR User provisioned before migration is placed in a reconciliation queue for the customer's admin.

Nextal custom fields on Jobs require field-level mapping to BambooHR custom fields. We extract the Nextal field schema including field label, data type, and picklist values, then create matching custom fields in BambooHR's Employee or Job module. Text fields map to BambooHR Text custom fields; date fields map to Date fields; picklist fields map to Dropdown fields with values migrated from Nextal. Fields that exist in Nextal but have no BambooHR equivalent are created as custom fields or flagged for the customer to prioritize post-migration.

Nextal custom fields on Candidates require field-level mapping to BambooHR Employee custom fields. We follow the same field extraction and type-mapping process as Job custom fields. BambooHR's employee data model has specific field type restrictions (Information fields, Section headers, and Multiple Selection List fields cannot be passed via the BambooHR API), so we flag any Nextal candidate custom fields that fall into these restricted categories and document them for manual entry or alternative handling.

Resume and document attachments on Nextal Candidate records migrate to BambooHR Employee Files. We extract files by candidate, preserve the original file name and format (PDF, DOCX, RTF), and upload them as Employee File attachments linked to the corresponding BambooHR Employee record. BambooHR supports file storage on Employee records with file type categorization (Resume, Offer Letter, Other). File download URLs from Nextal are preserved in a BambooHR custom field for cases where the original file cannot be directly transferred.

Nextal multilingual email templates tied to job stages migrate as BambooHR email templates. We extract templates as HTML blobs with merge field placeholders and import them into BambooHR's template library. Language variants are preserved as separate template versions. BambooHR email templates use a different merge field syntax than Nextal, so we transform merge fields during extraction (e.g., Nextal {{candidate.first_name}} becomes BambooHR {{employee.firstName}}). Automated candidate communication sequences and stage-triggered emails do not migrate as automation; we document them as rebuild requirements for BambooHR workflows.

Nextal interview scorecards and interviewer feedback attached to Applications migrate to BambooHR Notes on the corresponding Job Application or Employee record. We extract structured scorecard data as formatted Note content with field labels preserved. Interview scheduling data (if available in Nextal) migrates as Note content with date and time preserved. Live calendar integrations and scheduling links do not transfer; these require reconfiguration in BambooHR's scheduling settings.