Migrate from Martian Logic to BambooHR

Martian Logic's Employee Database records map directly to BambooHR Employee. All personal details (name, date of birth, contact information, emergency contacts, address history) migrate as typed BambooHR fields. Martian Logic stores custom folders of additional data per employee (certifications, compliance documents, file attachments); we map each configured folder to a corresponding BambooHR custom field, creating the field in BambooHR first and then populating it. Historical employment status (active, on leave, terminated) migrates with the employee's termination date and reason preserved if applicable.

Martian Logic Positions are first-class objects linked to employees and forming the org chart hierarchy. BambooHR has no Position object; instead, we split each Position into a Department (derived from the Position's organisational unit) and a Job Information entry (title, FTE, location, manager). The Position's reporting chain becomes the BambooHR reporting structure under Employee > Manager. Positions archived or soft-deleted in Martian Logic require cleanup before migration to avoid orphaned nodes in the destination hierarchy.

The Martian Logic org chart is a derived view of Position-to-Position reporting chains, not a standalone object. We walk the Position hierarchy by resolving each position's reportsTo relationship, then reconstruct it in BambooHR by setting each employee's manager field to the employee who holds the parent Position. If the same Position is held by multiple employees (e.g., a role shared across a department), the primary incumbent maps to the manager field and additional holders are linked as department peers.

Martian Logic Change of Staff Conditions records are effective-dated transactions with fields for change type, old value, new value, reason, and effective date. BambooHR does not store a transaction log of changes; instead, the current Job Information fields reflect the latest state. We flatten the change history into a per-employee custom field (a text block or a series of dated custom fields) that logs each change as a line item: date, change type, old value, new value. Customers who need full audit history retain it as a readable log rather than as queryable records.

Onboarding e-forms in Martian Logic store field values as configuration-dependent JSON payloads that vary by employer pack. There is no fixed schema across packs. We parse each employee's onboarding payload during extraction, build a per-pack field mapping, and create matching custom fields in BambooHR. Fields present in the source payload but with no BambooHR equivalent become free-text custom fields. BambooHR custom field creation is admin-accessible and does not require developer credentials, so the customer can add additional fields post-migration if needed.

Martian Logic stores compensation against or linked to Positions via the Role and Remuneration Library (base salary, allowances, pay frequency, effective-from date). We extract the most recent compensation record per employee and map base salary to BambooHR's payRate field. Allowances (car, phone, superannuation, bonus) migrate as a custom field group. BambooHR does not natively support effective-dated compensation history as a separate object; we store the latest compensation snapshot and log historical pay changes in the Employment Change history custom field.

Martian Logic ATS manages candidates through the full pipeline including requisition, application, interview score, and offer. If BambooHR Applicant Tracking is in use at the destination, we map Candidates to BambooHR Applicants with status history, application dates, and interview scores preserved as custom fields. If BambooHR ATS is not activated, candidates cannot be imported and we document the open requisitions and pipeline stages as a written inventory for the customer's admin to recreate manually or in a dedicated ATS tool. BambooHR ATS is a priced add-on; scoping must confirm whether it is active at the destination.

Open and closed requisitions in Martian Logic (including requesting manager, approved headcount, status, and creation date) map to BambooHR Job Openings if the BambooHR ATS module is active. The requisition approval workflow is a Martian Logic configuration artefact that does not export; we document each open requisition's details and status so the customer can recreate the opening in BambooHR ATS without losing the hiring context.

Martian Logic Integration Connectors push employee data to third-party payroll systems with custom field-to-field mappings. These connector configurations are not exportable from Martian Logic. We document every active connector's source field, destination field, and trigger condition during discovery. The equivalent integration must be rebuilt in BambooHR's native integrations or via a middleware tool (such as Zapier or Workato). BambooHR has a published integration catalogue; customers moving from Martian Logic's STP-integrated payroll tier should note that BambooHR Payroll is not available in Australia and will require a separate payroll product.

Martian Logic stores Employee Self-Service access levels and role permissions per employee or per role. BambooHR uses a role-based permission model (Employee, HR Admin, Manager, Super Admin) applied at the user level rather than per field. We export ESS access as a custom field on the employee record (e.g., can_approve_leave: Yes/No, can_view_payroll: Yes/No) so the information is preserved even though the permission enforcement model differs. Customers with role-based access configurations spanning many levels may need to rationalise the access model as part of the migration.