Migrate from Manatal to BambooHR

Manatal Candidates map to either BambooHR Applicant or Employee depending on their pipeline status. Candidates at a Hired or Placed stage migrate as BambooHR Employees with hire date, department, job title, and salary if present. Candidates still in the recruiting pipeline migrate as BambooHR Applicants with source attribution and the original Manatal candidate ID preserved in a custom field for reconciliation. The split decision is made at migration time based on Manatal pipeline stage values provided during scoping.

Manatal custom fields on Candidates migrate to BambooHR Employee Custom Fields. BambooHR supports text, number, date, dropdown, checkbox, and paragraph field types. We map the Manatal field data type to the nearest BambooHR equivalent. Custom field categories in Manatal do not have a direct BambooHR analog; all migrated custom fields attach directly to the Employee record. We preserve the original Manatal field name in the BambooHR custom field label for audit traceability.

Manatal tags on Candidates migrate to BambooHR Employee Custom Fields of type paragraph or multi-value text. Each unique tag from Manatal becomes a separate custom field in BambooHR or is concatenated into a single comma-separated custom field based on customer preference during scoping. Tag preservation supports ongoing candidate sourcing analytics after migration.

Manatal activity logs (stage transitions, user actions, notes) are mapped to Employee Custom Fields where the activity is a single date or state change, or to Document records in BambooHR for narrative content. High-volume activity logs with hundreds of entries per candidate are summarized or sampled based on customer scope; we do not migrate every individual activity log entry unless specifically agreed. We preserve the most recent 12 months of activity by default.

Manatal resume files attached to Candidates migrate as Documents in BambooHR linked to the corresponding Employee. We transfer file metadata (filename, upload date, file type) and preserve the original file reference. Binary file transfer depends on Manatal's export capabilities at the time of migration; if API access is unavailable, we fall back to admin-panel download. PDF and DOCX formats are preserved directly; other formats may require conversion.

Manatal Organizations (representing clients or internal departments) map to BambooHR Departments. The organization name becomes the department name. We extract department heads from Manatal organization records where assigned and map them to the BambooHR department manager field. Organizations representing external clients (a Manatal CRM feature) do not have a direct BambooHR equivalent; we document these in the reconciliation report for the customer to evaluate whether they require a separate CRM or manual tracking in BambooHR.

Manatal Job records map to BambooHR job postings with limitations. BambooHR job postings capture the job title, description, department, status (Draft, Open, Filled, Closed), and source attribution. Pipeline stages, candidate-to-stage assignments, and vacancy limits from Manatal do not migrate because BambooHR ATS does not support a multi-stage pipeline model. The original Manatal job ID and pipeline stage at time of migration are preserved as custom fields on the BambooHR Employee or Applicant record for audit.

Manatal pipeline stages are not migratable to BambooHR because BambooHR ATS does not have a configurable stage model. We document every pipeline stage name, order, and candidate count per job in a written stage inventory. The customer's admin uses this inventory to understand which candidates were at which stage before migration and to manually update hiring status in BambooHR post-migration.

Manatal user accounts with recruiter or admin roles are migrated as BambooHR Employees. We preserve the Manatal role assignment as a custom field on the BambooHR Employee record. Manatal user IDs are preserved in a custom field for reconciliation. SSO configuration and User Groups from Manatal do not migrate to BambooHR; we document these in the automation inventory for the customer's IT team to configure post-migration.

Manatal workflow automations (Enterprise and Enterprise Plus plans only) are not migratable to BambooHR because BambooHR does not expose a workflow automation API or rule engine. We document every active automation with its trigger conditions, actions, and affected record types in a written handoff document. The customer's admin evaluates the document against BambooHR's available features (built-in workflows, BambooHRтан by Marketplace partners, or manual process) and rebuilds as appropriate post-migration.

Manatal includes CRM features for staffing agencies tracking client placements and commission revenue. These records do not have a BambooHR equivalent because BambooHR is an HRIS, not a staffing CRM. We extract placement and revenue data from Manatal into a structured CSV export and deliver it alongside the migration for the customer to import into a separate CRM or analytics tool. This is explicitly outside the standard BambooHR migration scope.