Migrate from Attendo to HubSpot Service Hub

Attendo Employees map to HubSpot Contacts as the primary person record. Standard fields (name, role, department, start date) map directly to Contact properties. Attendo custom fields on employee records migrate as HubSpot custom contact properties. The migration user email must be provisioned in HubSpot Service Hub before import so that OwnerId references are satisfied. Historical employment status changes are preserved as a custom field for audit. Attendo's lack of a public API means we design the employee export from file dumps or database extracts before any HubSpot import pipeline runs.

Attendo attendance entries (clock-in/out events, overtime, breaks, exception flags) map to a HubSpot custom object of the same name. Each attendance record carries a lookup to the Contact (from the Employee mapping) via a contact_id property. Overtime flag, break duration, and work-time exception codes migrate as custom fields on the attendance custom object. We create the custom object schema in HubSpot before migration using the HubSpot CRM API, including all field types (number for duration, date for timestamps, enumeration for exception type).

Attendo PTO policy definitions (accrual rate, carryover rule, ceiling limit, policy type) migrate to a HubSpot custom object named PTO Policy. Each policy record links to the Contacts to which it applies via a multi-select contact lookup or a junction object. Accrual balance at migration time is captured as a snapshot custom field on the attendance custom object rather than a live-calculated field, since HubSpot does not have native accrual computation.

Attendo Absence Plans (sick leave, vacation, unpaid leave) migrate to a HubSpot custom object with policy type, start date, end date, and status fields. Per-employee overrides in Attendo are preserved as individual absence records linked to the Contact. The balance remaining at migration time is stored as a snapshot field; no live accrual logic carries over.

Attendo projects are mapped to HubSpot Deals if the project represents a billable service engagement with a client. Projects that represent internal workforce assignments without a revenue line map to a custom Project object in HubSpot. We determine the classification during scoping based on whether the project has an associated customer. Project cost data (labour, materials, fixed-cost line items) migrates as custom fields on the destination record; we flag any HubSpot account structure differences for the customer admin to resolve.

Attendo Tasks map to HubSpot Tasks. Each task carries a reference to its parent project record (Deal or custom Project object). Task status values (not started, in progress, completed, blocked) map to HubSpot Task status with a custom enumeration mapping table produced during discovery. Assignee is resolved by matching the Attendo employee identifier to the HubSpot Contact (from the Employee mapping). Deadlines migrate as HubSpot Task Due Date.

Attendo cost tracking data (labour, materials, fixed-cost line items against project budgets) migrates as a set of custom fields on the destination project record (Deal or custom Project object). We map Attendo cost category names to HubSpot custom field labels and create the fields during schema setup. Any chart-of-accounts structure from Attendo is preserved as field labels and a mapping table for the customer admin to align with their HubSpot reporting structure.

Employee contracts, offer letters, and supporting HR documents export as binary files from Attendo. We re-associate each file with its corresponding Contact record in HubSpot using a deterministic naming convention (employee ID or email) and upload as HubSpot Files attached to the Contact. The original filename and MIME type are preserved. Files without a resolvable Contact are placed in a reconciliation queue during migration.

Attendo custom fields on employee and project records are exported alongside the data as a schema manifest. We recreate each custom field in HubSpot as a custom contact property or custom object field before data import begins. Field type mapping follows Attendo type to HubSpot type (text to single-line text, number to number, date to date, enumeration to single- or multi-select picklist). The customer reviews the field mapping table and approves or modifies it before migration runs.

Attendo internal system messaging tied to workflows is transient inter-employee communication and does not constitute a formal business record. It does not migrate. We note its exclusion in the scope document. If audit or compliance requires preservation of any message content, we can export it as a flat file for the customer's records but it does not load into HubSpot Service Hub as a standard object.

Attendo employee owners referenced on projects and tasks are resolved by matching the employee email to a HubSpot User record. We require the customer to provision HubSpot Users for all active Attendo owners before migration begins. Inactive or terminated employees are migrated as Contacts without a HubSpot User record; owner history is preserved as a custom text field on the record.

If the customer has been using Attendo's ticket or case management feature (identified during discovery), those records map to HubSpot Service Hub Tickets. Ticket status maps to HubSpot Ticket status, priority maps to HubSpot Ticket priority, and the customer contact reference maps to the HubSpot Contact record. Conversation threads migrate as Ticket conversation entries.