Migrate from Attendo to Salesforce Service Cloud

Attendo employee records map to Salesforce Contact with the employing organization represented as an Account. Name, role, department, start date, employment status, and contact details migrate as Contact fields. We preserve historical employment status transitions as a custom field on the Contact record. If Attendo stores department as a separate entity, we pre-create the Account as a hierarchical organization unit and link each Contact via the ReportsToId or a custom organization hierarchy field.

Attendo clock-in/out events and work-time entries migrate to a custom Attendance_Record__c object with a Lookup to the Contact (employee). Each record carries the clock-in timestamp, clock-out timestamp, work hours, overtime flags, break duration, and exception flags as typed fields. The Attendance_Record__c custom object is pre-created before employee migration so the Contact-attendance lookup resolves at insert time. Historical attendance data volume (number of years retained) determines the batch load duration via the Salesforce Bulk API.

Attendo project records (with timelines, budgets, progress indicators, and cost allocations) map to a custom Project__c object. We map the Attendo project name, start date, end date, budget, status, and description fields to the corresponding Project__c fields. The primary Contact (project manager or lead) on the Attendo project migrates as a Lookup to the Contact record resolved via email match. If the customer uses Salesforce Account teams, we configure the project as related to the responsible Account.

Attendo tasks belonging to projects migrate to Salesforce Task with the WhatId pointing to the Project__c custom object and the Subject, Status, Priority, ActivityDate, and Description fields mapped directly. Task assignees resolve via email match against Salesforce Users (owner assignment) and Contacts (assigned-to contact). Attendo task status values map to Salesforce Task Status using a configurable status bridge table created during scoping.

Attendo absence plans define policy type (sick, vacation, unpaid), accrual rates, and current balance per employee. We create an Absence_Balance__c custom object with fields for balance type, accrual rate, carryover balance, ceiling, and the Contact lookup. The balance snapshot migrates at migration time as a static record — accrual logic does not carry over and must be reconfigured in Salesforce using a PTO management app from the AppExchange or custom Flow logic post-migration. Each employee may have multiple Absence_Balance__c records (one per policy type).

Attendo's configurable PTO policy definitions (accrual rates, carryover rules, ceiling limits) map to a PTO_Policy__c custom object as configuration records rather than active balances. The policy may apply to a subset of employees represented by a junction object (Employee_Policy_Assignment__c) linking Contact to PTO_Policy__c. We export the policy definition as structured data and flag any per-employee overrides for review before they are recreated in Salesforce Flow or a PTO management application.

Attendo project-level cost data (labour, materials, fixed-cost line items) maps to a Project_Cost__c custom object with a Lookup to Project__c. Cost categories map to a custom picklist aligned with the destination's chart-of-accounts structure. We flag any cost allocations that do not fit a standard Salesforce field type for manual review and mapping adjustment during the sandbox validation phase. Currency fields use the organization's default currency ISO code.

Attendo configurable fields on employee and project records map to Salesforce custom fields on Contact, Project__c, and related objects. We export the full Attendo field schema (field name, data type, picklist values) before migration and pre-create the corresponding Salesforce fields using the Salesforce Metadata API. Field type mapping is applied per the standard type translation table: text to Text(255), number to Number, date to Date, checkbox to Boolean, and multi-select picklists to Multi-Select Picklist.

Employee contracts, offer letters, and supporting documents stored as binary files in Attendo export as file blobs. We upload them to Salesforce as ContentDocument records via the Chatter API or Bulk API, then create ContentDocumentLink records linking each document to the relevant Contact. File naming preserves the original Attendo filename and applies a migration tag in the Description field for identification. Large document volumes require the ContentDocument migration to run after the Contact load completes so that parent IDs are available.

Attendo owner or manager references on employee, project, and task records map to Salesforce User via email match. We extract every distinct owner reference from Attendo and match by email against the Salesforce destination org's User table. Any owner without a matching User goes to a reconciliation queue for the customer's admin to provision before the migration resumes. Owner assignment on migrated Tasks sets the Task OwnerId using the resolved User reference.