Migrate from Accelo to Salesforce Sales Cloud

Accelo Companies map directly to Salesforce Account. The Company id becomes the external ID on Account for deduplication. All Company-level custom fields supported via Accelo's API at /affairs migrate as typed Salesforce custom fields. Address, industry, and category metadata map to standard Account fields.

Accelo Contacts map to Salesforce Contact. Contact-to-Company association maps to AccountId via the Company-to-Account lookup. Email deduplication is enforced on insert. All Contact-level custom fields supported via Accelo's /contacts API migrate directly. Phone, mobile, title, and address fields map to Salesforce standard fields.

Accelo Deals map to Salesforce Opportunity with the pipeline-to-Record Type mapping configured during scoping. Deal value, stage, close date, and owner assignment migrate. Accelo's single deal pipeline becomes a Salesforce Sales Process with stage values aligned to the customer's deal lifecycle. Closed-Lost and Closed-Won outcomes map to Salesforce StageName outcomes.

Accelo Jobs are the core project object and do not have a direct Salesforce equivalent because Salesforce is a CRM, not a PSA. For service firms that track project-based deals, we map Jobs to Salesforce Opportunity with a custom Job metadata section (custom fields for phase, milestone, assignee). For firms that need full project hierarchy, we propose a Project custom object with Phase and Task child custom objects. The customer chooses during scoping.

Accelo Job phases migrate as a custom multi-select picklist on Opportunity (for simple phase tracking) or as Phase records in a Project hierarchy custom object. Phase status (active, paused, complete) maps to a custom status field.

Accelo Tasks map to Salesforce Task with Status, Priority, ActivityDate, and description preserved. Assignee resolves via Staff-to-User mapping by email. Checklist items within Accelo Tasks migrate as child Task rows with a parent reference. Custom fields on Tasks are not accessible via Accelo's public API and are flagged for manual post-migration entry or CSV extraction if available.

Accelo Time Entries do not have a Salesforce native equivalent. We create a custom Time_Entry__c object with fields for Hours, Billable_Flag__c, Rate__c, Date__c, and Job__c (lookup to Opportunity or Project). Billable rate metadata preserves as Rate__c because Salesforce Opportunity does not natively support per-task billable rates. Large time entry sets require pagination through Accelo's API since no bulk export endpoint exists.

Accelo Tickets map to Salesforce Case if the destination org includes Service Cloud. Ticket status, priority, type, assignee, and description migrate. Ticket custom fields and categories are fully supported. Conversation threads migrate as EmailMessage records linked to the Case. If the destination org does not include Service Cloud, Tickets migrate to a custom Support_Ticket__c object.

Accelo Staff records map to Salesforce User. We match by email as the dedupe key. Accelo distinguishes Staff (delivery users) from broader user records, which may affect permission set assignments post-migration. Staff without matching Salesforce Users are held in a reconciliation queue for the admin to provision before migration continues.

Accelo Leads export via the Sales API with source, status, owner, and custom fields. Leads map to Salesforce Lead. Owner resolves via Staff-to-User mapping. The original Accelo Lead source and status values map to Salesforce Lead Status and LeadSource picklists configured to match the customer's values.

Accelo Retainers are a compound object combining contract terms, prepaid balance, and billing rules. We separate Retainer metadata (contract dates, client, value) from the associated Invoice and time entry records. Retainer balance data cannot migrate as live financial records into Salesforce without Salesforce Billing. We map Retainer contract metadata to a Salesforce Contract or a custom Retainer__c object and flag the billing component for post-migration setup in Salesforce Billing or a third-party billing tool.

Accelo Invoices export from the 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 map Invoice metadata to a custom Invoice__c object linked to Account. Line items map to custom Invoice_Line_Item__c records. We flag the lack of native billing reconciliation in Salesforce for the customer's finance team to handle separately.

Attachments on Jobs, Tasks, and Tickets export via /attachments. We download file content individually and re-upload to Salesforce as ContentDocument records linked via ContentDocumentLink to the parent record (Opportunity, Task, or Case). Filename and linked object association are preserved.

Ticket comments export via the Tickets API with author, timestamp, and visibility preserved. We map them to Salesforce EmailMessage records linked to the Case. Thread ordering is maintained by ActivityDate. Comments on Tasks and Jobs use a separate endpoint and migrate to Task or Note depending on visibility settings.