Migrate from Atendare to Twenty CRM

Atendare Contact records map to Twenty Person objects. We extract first name, last name, email addresses, phone numbers, lifecycle stage, segmentation tags, and custom properties. The Person record is created before any related Opportunity to satisfy Twenty's relational foreign key requirements. Email addresses migrate as multiple Email objects linked to the Person rather than a single multi-value field, matching Twenty's data model.

Atendare Company records map directly to Twenty Company objects. We preserve the company name, domain, industry, employee count, and address fields. The Company record is created before any Contact import so that the Person-Company relationship is resolved at insert time. Company-level custom fields map to Twenty custom fields on the Company object.

Atendare Deals map to Twenty Opportunity records. We extract deal name, value, stage, expected close date, owner assignment, and associated Company and Contact links. Atendare's deal value (currency-typed in BRL or another configured currency) maps to the Opportunity amount field. Owner assignment resolves via email match against Twenty WorkspaceMember records.

Atendare pipeline stage names and ordering migrate to Twenty's Stage configuration. Each Atendare pipeline becomes a separate set of Stage values within Twenty's workspace. If Atendare has multiple named pipelines, we map them as stage groups or as separate Opportunity records with a custom pipeline-name field. Stage probabilities from Atendare migrate as stage_order or custom numeric fields since Twenty does not have a native probability field.

Atendare multiple-activity types (calls, meetings, tasks) map to Twenty Task records with the type differentiated by a custom type field or task title prefix. Timestamps, descriptions, and owner assignments preserve during migration. Tasks link to the related Person or Opportunity via Twenty's relational fields. We validate that ActivityDate maps to the Task display date before insert.

Custom fields on Atendare Contacts, Companies, and Deals migrate to Twenty custom fields on the equivalent object. We detect all custom property definitions during discovery, map Atendare field types (text, number, date, dropdown, checkbox) to Twenty's custom field type system, and flag any multi-select or multi-checkbox properties that may require special handling or a custom field type approach in Twenty.

Atendare users mapped to Twenty WorkspaceMember records by email address. We extract user name, email, and role where available. If the destination is a self-hosted Twenty instance, we coordinate with the customer to provision users in Twenty's admin settings before migration. Any Atendare user without a matching Twenty account goes to a reconciliation queue.

Atendare Proposals are Enterprise-tier objects with no direct Twenty equivalent. We extract proposal name, line items, totals, and status as Opportunity records with a note flagging the original proposal origin. Any attached PDF or document is flagged for manual upload to the related Twenty Opportunity record. This is a data-loss disclosure we document explicitly before migration begins.

Atendare Product Catalog items (name, SKU, description, price) migrate as Twenty custom records or as Opportunity line item entries depending on the Twenty version deployed. We extract the product-to-deal associations and map them as Opportunity-related custom product entries. If the Twenty instance has no native product object, we rebuild the product list as a custom table within Twenty's data model.

Atendare contact segments defined by filter rules migrate as saved filter criteria documented in a written handoff. Twenty does not have a native segment object equivalent; we recommend rebuilding segments as Twenty Filters (which are named saved views) or tagging records with a segment-identifier custom field. The customer chooses the rebuild strategy during scoping.