Migrate from Apptivo to Twenty CRM

Apptivo Contact records map to Twenty CRM Person objects. We resolve the full name split (first_name, last_name from Apptivo's combined name field), email addresses map to emails array, phone to phone_numbers, and postal addresses to address fields. Custom attributes on the Contacts app map to custom fields on the Person object. Per-app custom fields are enumerated individually during discovery because Apptivo's Contacts app has its own Master Layout independent of other apps.

Apptivo Lead records map to Twenty CRM Person objects with a personType field set to 'Lead' for segregation. Lead scoring, source tracking, and lifecycle stage from Apptivo map to custom fields on the Person record. If the lead has been qualified into a Customer or Opportunity in Apptivo, we create the corresponding Person record in Twenty and link the Opportunity.

Apptivo Customer records (B2B account objects) map to Twenty CRM Company objects. Company name, website, industry, employee count, and billing address migrate directly. We preserve the association between Customer and any linked Contacts by creating the Company record first, then resolving the companyId on each related Person record during import. Apptivo Customer records do not have a direct pipeline or deal association; deal data lives in the Opportunities app.

Apptivo Opportunity records map to Twenty CRM Opportunity with pipeline stage, deal amount, expected close date, and probability. We map Apptivo stage names to Twenty's pipeline stage values. Closed-Won and Closed-Lost reasons from Apptivo custom fields migrate to custom fields on the Twenty Opportunity record. Owner assignment resolves by email match against Twenty User records.

Apptivo Cases (helpdesk tickets) map to Twenty CRM Task records with a custom taskType or a dedicated Case custom object if the workspace has one configured. Case status, priority, owner, and conversation threads migrate. The Apptivo Case conversation history migrates as linked Note records or Task comments depending on the Twenty version. We flag any Cases that reference Contacts or Customers not yet migrated and hold those for a second-pass resolution.

Apptivo Project records migrate to a Twenty CRM custom object named Project if the customer's data model warrants a dedicated object, or to Task with a projectType flag for simpler models. Project task hierarchies (milestones, sub-tasks, assignees) migrate as nested Task records with a parentId reference. Customer portal settings on Apptivo Projects do not migrate because Twenty does not have an equivalent customer portal feature in v1.

Apptivo Invoice records map to a Twenty CRM custom Invoice object created during schema setup. Invoice headers (invoice number, date, due date, status) migrate. Line items migrate as a related custom object or as a JSON field on the Invoice object depending on the customer's reporting needs. Partial payment records require manual review post-migration because payment status tracking differs between platforms.

Apptivo Items (product and service catalog) map to a Twenty CRM Product custom object with name, description, price, and SKU fields. Text, number, date, and dropdown custom attributes on Apptivo Items migrate to corresponding custom fields on the Product object. Items linked to Invoices are reconciled after the Product records land so that line item relationships resolve correctly.

Apptivo Employee records map to Twenty CRM WorkspaceMember objects. Contact info, job title, department, and employment status migrate. We use email as the match key against existing Twenty users. Any Employee records in Apptivo that do not correspond to an active Twenty workspace member are held in a reconciliation queue for the customer's admin to provision access before the final record import.

Each Apptivo app has its own Master Layout with independent custom attribute sets. A single attribute name (e.g., 'Region') may appear in multiple apps as a completely different field. We enumerate all custom attributes per app during discovery, create corresponding custom fields on the relevant Twenty object during schema setup, and map each attribute to its app-scoped destination. The customer chooses whether to consolidate duplicate attribute names across apps into a single Twenty field or keep them separate.

File attachments on Apptivo records migrate as Twenty File records linked to the parent object (Person, Company, Opportunity, Task) via a foreign key. Large attachments may require chunked upload handling. We preserve the original filename, MIME type, and upload timestamp. Attachments exceeding 10 MB are flagged for the customer to re-upload manually if storage constraints apply on the self-hosted instance.