Migrate from Accelo to Pipedrive

Accelo Companies map directly to Pipedrive Organizations. The company name, address, industry, and category fields migrate via the /affairs endpoint. We preserve company-level custom fields (the only Accelo objects with full API custom field support) as Pipedrive custom fields on Organization. Company is created before Contact import so that OrganizationId is available for the contact-to-company link.

Accelo Contacts map to Pipedrive Persons. First name, surname, email, phone, mobile, title, and address fields migrate via /contacts. Custom fields on Contacts (the second Accelo object with full API support) map to Pipedrive Person custom fields. Email is used as the dedupe key. Contact-to-Company association resolves via OrganizationId lookup after Organizations are imported.

Accelo Deals from the Sales module map to Pipedrive Deals. Deal name, value, stage, owner, and close date migrate. Stage names differ: Accelo uses its own stage labels while Pipedrive uses pipeline-specific stages. We configure Pipedrive pipelines and stages to match Accelo's sales stage names during schema setup. Closed-won and Closed-lost statuses map directly.

Accelo Jobs (the core project object) have no direct Pipedrive equivalent. We map Jobs to Pipedrive Activities with a custom field job_type__c set to 'job' to distinguish them from standard sales activities. Job phases become Activity subject prefixes or notes. Milestone dates migrate as Activity due dates on milestone-related activities. The customer decides during scoping whether to use a separate Pipedrive pipeline for project work or tag within the sales pipeline.

Accelo Tasks map to Pipedrive Activities. Subject, description, assignee (resolved via Staff-to-User lookup), due date, and status migrate. Checklist items within Accelo tasks become separate Activity records linked by a parent_task_id__c custom field. Task priority maps to Pipedrive Activity priority values.

Accelo Tickets (support module) map to Pipedrive Activities with a custom field ticket_type__c set to 'ticket' to distinguish from sales activities. Ticket status, priority, and type migrate to Activity custom fields. Ticket conversations (comments) migrate as separate Activity notes linked by ticket_id__c. Pipedrive has no native ticket object, so support queues require manual setup of Pipedrive's built-in helpdesk or a third-party integration post-migration.

Accelo Staff records (delivery users) map to Pipedrive Users. We resolve by email match. Any Accelo Staff member without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision. Staff with the 'portal' role (client-facing) may be better mapped as Persons rather than Users depending on whether the customer wants clients in Pipedrive.

Accelo Time Entries have no native Pipedrive equivalent. We transform each time entry into a Pipedrive Activity record with custom fields: time_entry_rate__c (billable rate), time_entry_hours__c (duration in hours), time_entry_billable__c (boolean), and time_entry_job_id__c (linked to the mapped Job Activity). This preserves the financial metadata for reporting even though Pipedrive cannot generate invoices.

Accelo Retainers (compound contract + prepaid balance + billing rules) do not map to any Pipedrive object. We separate retainer metadata into: a Pipedrive Deal with status ' retainer' capturing client, contract value, start date, and end date; and a written retainer summary document delivered alongside migration for the customer's admin to maintain in a spreadsheet or billing tool. Retainer prepaid balance is documented but cannot be tracked in Pipedrive's financial model.

Accelo Invoices have no native Pipedrive equivalent. We map invoice records to closed-won Deals with a custom field original_invoice_id__c and invoice_status__c (paid, partial, overdue). Line item amounts roll into the Deal value. Invoice PDFs are downloaded from Accelo and re-uploaded as Files attached to the mapped Deal in Pipedrive. Ongoing invoice generation requires a third-party billing integration post-migration.

Accelo Leads from the Sales module map to Pipedrive Leads if the customer uses Pipedrive's optional Lead inbox, or to Persons if they work directly in the deal pipeline. The customer chooses during scoping. Lead source, status, owner, and custom fields migrate. If mapped to Person, the Lead is created with a lead_source__c custom field carrying the original lead data.