Migrate from Accelo to Twenty CRM

Accelo Companies export via /affairs with full custom field support. Map directly to Twenty Company object. The company name becomes Company.displayName, address maps to the Company address fields, and industry maps to a custom picklist field if Twenty's industry field is not configured. Company-to-contact relationships resolve during the Contact import phase.

Accelo Contacts export via /contacts with first name, surname, email, phone, and custom fields. Map to Twenty People object. Contact-to-company links resolve via the Company mapping, attaching each People record to the correct Company via the Twenty relationship field. Email deduplication runs against the People.email field before insert.

Accelo Deals export via the Sales API and map to Twenty Opportunity. We preserve deal value, stage name, owner assignment, and custom fields. Accelo Deal stages map to Twenty Opportunity stage values, which we configure during workspace setup. Closed-won and closed-lost states and dates migrate as custom fields if the standard schema does not include them.

Accelo Jobs have no native Twenty equivalent. We create a Project custom object via Twenty's /metadata API with fields for title, description, status, start date, due date, assigned user, and related company. Phases within a Job map to sub-tasks or a Phase custom field. The customer chooses whether to migrate open Jobs only or include historical completed Jobs based on business value.

Accelo Tasks export from /tasks with assignees, checklists, due dates, and custom fields. Checklist items within tasks preserve as sub-task rows. Task statuses map to Twenty Task status values configured during workspace setup. Tasks linked to Jobs resolve to the Project custom object created during Jobs migration.

Accelo Tickets have no native Twenty equivalent. We create a Support Ticket custom object with fields for subject, description, status, priority, type, assignee, and related company or contact. Ticket conversations and comments migrate as Note records attached to the custom Ticket object. Custom ticket fields map to custom fields on the Ticket custom object.

Accelo Time Entries have no native Twenty equivalent. We create a TimeEntry custom object with fields for hours, billable flag, rate, date, related task or job, and staff member. Billable/non-billable status preserves as a boolean field. We flag Time Entries that reference archived Jobs or Retainers for the customer to review before migration.

Accelo Staff records export via /staff and map to Twenty WorkspaceMember. Accelo distinguishes Staff (delivery users) from broader User records. We resolve by email match and flag any Staff without a matching Twenty workspace for admin provisioning before record import.

Accelo Leads export via the Sales API with source, status, owner, and custom fields. Depending on whether the customer treats Leads as prospects or unqualified Deals, we map to Twenty People (with a lead status custom field) or to Opportunity records without a company association. The customer decides during scoping.

Accelo Invoices carry financial data including line items, amounts, and status. Twenty has no native billing engine. We create an Invoice Record custom object to preserve historical invoice data as read-only records, but the customer must use a separate invoicing tool post-migration. We flag any Invoice records that reference retired chart-of-accounts entries during scoping.

Accelo Retainers combine contract terms, prepaid balance, and billing rules. We separate Retainer metadata (contract dates, client, value) into a Contract custom object in Twenty. Prepaid balance and billing rules have no Twenty equivalent; we preserve the balance as a custom field and flag the gap for the customer's admin. Accelo Payments fee structure (3.4% card fee plus $0.20) does not migrate.

Attachments on Jobs, Tasks, and Tickets export via /attachments. File content fetches individually. We download and re-upload to Twenty's file storage, preserving filename and linked object association. File type and size validation runs against Twenty's supported formats before upload.