Migrate from Attendo to Zoho Desk

Attendo Employee records map to Zoho Desk Contacts. The employee's name, email, phone, department, and job title transfer directly. We use the employee's email as the Contact dedupe key during import, matching Zoho Desk's required Email field. Any Attendo employee without an email address is flagged for manual review; Zoho Desk Contacts require an email under standard import rules. Custom properties on the employee record map to Zoho Desk custom fields scoped to the Contacts module, which require Support Administrator permissions to create.

Attendo Tasks with project associations map to Zoho Desk Tickets. The Attendo task name becomes the Ticket Subject, task description becomes the Ticket Description field, and task status (pending, in progress, completed) maps to Zoho Desk status values (Open, On Hold, Pending, Solved, Closed). Task assignees resolve by matching Attendo owner email to Zoho Desk agent email for ticket assignment. Tasks without a project association become standalone tickets assigned to a default department.

Attendo Projects map to Zoho Desk Accounts as a parent entity for related tickets. The project name becomes the Account Name, and project description becomes the Account Description. If the Attendo project has an associated client contact, that contact is linked to the Account via the Contact-to-Account relationship. We create the Account first so that subsequent Ticket imports can resolve the AccountId lookup.

Attendo custom fields on Employee and Project records are exported with their data type (string, integer, currency, date, checkbox) and recreated as Zoho Desk custom fields in the appropriate module. Zoho Desk custom fields are scoped per department and require Support Administrator permission to configure. Field type mapping follows: Attendo string to Zoho Desk string, Attendo integer to Zoho Desk integer, Attendo currency to Zoho Desk currency, Attendo date to Zoho Desk date. Multi-select or checkbox fields on Attendo map to Zoho Desk multi-select picklists.

Attendo employee contracts and supporting documents are exported as binary files and re-associated in Zoho Desk as attachments on the corresponding Contact record. We map the Attendo document name to the Zoho Desk attachment filename and link it to the Contact using the Attachment object with a ParentId pointing to the ContactId. Large files exceeding Zoho Desk's 10 GB total migration ceiling are flagged; files over 10 GB require a support ticket to Zoho Desk support team.

Attendo clock-in/out events and work-time entries have no native Zoho Desk equivalent. Zoho Desk does not have a time tracking or attendance module. We export the attendance log as a reference CSV and flag it for the customer to store in an alternative system (Zoho Books for time tracking, a separate HR system, or a data warehouse). The attendance history is not imported into Zoho Desk as a functional record type.

Attendo PTO configurations — accrual rates, carryover rules, ceiling limits, and per-employee applied balances — have no Zoho Desk equivalent. Zoho Desk's absence management is limited to agent time-off scheduling, not policy-level accrual. We export the PTO policy definitions and per-employee balance snapshots as a reference CSV and flag them for handoff to an HR system or Zoho People if the customer licenses it separately.

Attendo Absence Plans (sick, vacation, unpaid) with per-employee entitlements and balance snapshots do not map to any Zoho Desk object. We preserve the balance at migration time as a snapshot CSV and flag each employee's current balance for the customer to record in their HR system post-migration. Zoho Desk agents can log time off as a separate availability record, but accrual tracking is outside Zoho Desk scope.

Attendo project-level cost data (labour, materials, fixed-cost line items) against budgets and timelines has no Zoho Desk equivalent. Zoho Desk is a support platform, not a project cost accounting system. We export cost line items as a reference CSV and flag the customer to handle project cost tracking in Zoho Books, Zoho Projects, or their existing accounting system.

Attendo's internal inter-employee communication tied to workflows is not migrated. This transient communication channel does not constitute a formal business record under standard migration scope and has no Zoho Desk equivalent. We note this absence in the migration inventory for the customer's awareness.

Attendo historical employment status changes (active, inactive, terminated) are preserved in Zoho Desk as entries in a custom text area field or appended to the Contact Description field. Zoho Desk does not have an employee lifecycle history object, so we flatten the status timeline into a text representation for audit purposes.

Zoho Desk Agents are the support team members who handle tickets. If the migration scope includes provisioning Zoho Desk agents from Attendo employee records, we map Attendo employees with support-related roles to Zoho Desk agent profiles. Agent creation requires Last Name (required), Email (required), and optionally First Name and Full Name. Existing Zoho Desk agents with matching emails are mapped to the incoming records rather than duplicated.