Migrate your Accelo data

Companies are exported via Accelo's REST API at /affairs with full support for custom fields and categories. We preserve all company-level metadata including address, industry, and related contact associations. Duplicate detection during import is handled via company name matching.

Contacts export via /contacts with first name, surname, email, phone, and custom fields. CSV bulk import is also supported with duplicate detection and merge logic. We preserve contact-to-company associations and any custom properties.

Deals export via the Sales API and map to Opportunities or Deals in destination CRMs. We preserve deal value, stage, owner assignment, and custom fields. Stage names require mapping since Accelo uses its own status taxonomy that varies by deployment.

Jobs are Accelo's core project object and export via /affairs with phases, milestones, assignees, and dates. We transform Job phases into project phases or sub-projects depending on destination schema. Budget and rate information is preserved but may require custom field mapping at the destination.

Tasks export from /tasks with assignees, checklists, due dates, and custom fields. Checklist items within tasks are preserved as sub-task rows. We map Accelo task statuses to destination pipeline stages and flag any tasks linked to archived Jobs that may not carry over cleanly.

Time entries export via /time with billable flags, rates, and associations to Jobs, Tasks, and Staff. No bulk endpoint exists, so large time entry sets require pagination. We preserve billable/non-billable designation, rate, and duration — but time entry history may need date-range scoping for very large datasets.

Staff records export via /staff and map to Users in the destination system. Accelo distinguishes Staff (delivery users) from broader User records, which may require permission reconfiguration post-migration. We preserve email, name, role, and rate information.

Tickets export via /tickets with status, priority, type, assignee, and description. Custom ticket fields and categories are fully supported. We map ticket statuses to destination ticket statuses and preserve any linked client and contact associations.

Attachments on Jobs, Tasks, and Tickets export via /attachments. File content is fetched individually. We download and re-upload attachments to the destination, preserving filename and linked object associations. Very large attachment volumes increase migration time.

Invoices export from Accelo's billing module with line items, amounts, status, and client association. Historical invoice records carry financial data that may reference retired chart-of-accounts entries. We preserve invoice content but flag any records with complex retainer credits or adjustments for manual review before import.

Retainers are a compound object combining contract terms, prepaid balance, and billing rules. We separate Retainer metadata (contract dates, client, value) from associated Invoice and time entry records for independent migration. Balance reconciliation may require post-migration verification.

Accelo's API supports custom fields for Companies and Contacts via the /affairs and /contacts endpoints. We preserve all custom field values including choice-based, text, and date fields. These map directly to custom properties in most destination CRMs.

Ticket comments export via the Tickets API. We preserve comment text, author, timestamp, and visibility settings. Thread ordering is maintained. Note that comments on Tasks and Jobs use a separate endpoint and may require additional API calls to capture fully.

Leads export via the Sales API with source, status, owner, and custom fields. We map Leads to the destination's lead or contact object depending on whether the destination has a distinct Lead object. Lead status values are preserved as custom properties if a direct mapping is unavailable.