Migrate from Attendo to Intercom

Attendo Employee records map to Intercom Users as admin or teammate profiles. We extract employee name, email, department, role, start date, and employment status. Active employees become active Intercom users; inactive employees can be migrated as deactivated users to preserve historical context. The email address is the dedupe key. Note that Intercom Users are agent accounts for your support team, not customer contacts, so this mapping applies to your internal team rather than Attendo's external workforce data.

Attendo custom fields on employee records (department, cost center, employment type, location) map to Intercom User attributes. We export the Attendo field schema during discovery and recreate the same property structure in Intercom. Custom fields that reference other Attendo objects (such as a department lookup) are resolved to plain values during export to avoid broken references.

Attendo Projects with name, timeline, budget, and status can be stored as Intercom Custom Objects if your team wants to reference project context during customer support conversations. This is a reference-only mapping: project data lives in Intercom for context but does not drive workflows or routing. We create the Project Custom Object schema in Intercom (available from Advanced tier) and import records with external_id set to the Attendo project ID for traceability.

Attendo Tasks belonging to Projects map to Intercom Custom Object records with a parent-child relationship maintained via external_id references. If your support team needs to reference internal project task status during customer conversations, we store the task record in Intercom with a lookup back to the parent Project Custom Object. This is informational only; Intercom does not natively track task deadlines or assignees for internal project management.

Attendo PTO policies define accrual rates, carryover rules, ceiling limits, and per-employee overrides. Intercom has no equivalent object model for employee benefits or time-off tracking. We export the policy definitions as a JSON artifact for the customer's HR team to review, but these records do not load into Intercom. If the customer maintains a separate HRIS, the policy records remain there.

Attendo absence plans include policy type (sick, vacation, unpaid), accrual rates, and per-employee balance snapshots. Intercom does not model employee absence data. We take a balance snapshot at migration time and flag it for the customer's HR team to reconcile in their HRIS or payroll system. The absence history does not migrate to Intercom.

Attendo attendance records (clock-in/out events, work-time entries, overtime, breaks, exception flags) have no Intercom equivalent. Intercom is a customer support platform, not a timekeeping system, and does not track employee work hours. We do not migrate attendance logs to Intercom. If the customer requires attendance tracking post-migration, a dedicated time and attendance platform is the appropriate destination.

Attendo project cost tracking (labour costs, materials, fixed-cost line items against budgets) has no Intercom equivalent. Intercom does not track project budgets, cost allocations, or financial line items. These records remain in Attendo or move to a dedicated project management or PSA platform. We export a cost summary as a reference artifact.

Attendo binary documents attached to employee records (contracts, offer letters, supporting HR files) are exported as file blobs and re-associated in Intercom as ContentDocument records linked to the corresponding User profile. We preserve the original filename, mime type, and attached date. The document is uploaded to Intercom's file storage and linked via ContentDocumentLink to the User record.

Attendo internal system messaging stores inter-employee communication tied to workflows. This is transient communication that does not constitute a formal business record under standard migration scope. Intercom stores conversation history for customer contacts, not internal employee chat logs. We do not migrate internal messaging to Intercom.