Migrate from Ploomes CRM to Twenty CRM

Ploomes Contact records map to Twenty Person records. We extract all standard Contact properties (name, email, phone, address, social links) plus any CNPJ/CPF identification fields stored as custom properties on the Contact. These Brazilian business identification fields are preserved as custom fields on the Twenty Person record. Email address serves as the dedupe key during import. The Ploomes Contact-Company association is preserved by resolving the Organization ID before the Person import phase.

Ploomes Company records map to Twenty Organization records. Company name becomes the Organization name, domain maps to the Website field, and industry, employee count, and revenue fields map where present. Organization is the one-side of the one-to-many Person-Organization relationship, so we import Organizations first as Twenty's import documentation requires. Any Company-level custom fields are created as Organization custom fields in Twenty before import.

Ploomes Deal records map to Twenty Opportunity records. Deal name, value, stage, expected close date, owner, and probability percentages transfer directly. The Ploomes pipeline stage maps to a Twenty pipeline stage configuration that we set up before migration. Closed-Won and Closed-Lost reasons from Ploomes custom properties become Opportunity custom fields in Twenty. We resolve Organization and Person lookups before importing Opportunities so that the opportunity-account relationship is established at insert time.

Ploomes pipeline stages (associated with a specific Deal pipeline) map to Twenty pipeline stages. We create the destination pipeline structure in Twenty first, then configure stage order and probability percentages to match Ploomes. Stage assignments on Deals are preserved by matching stage names during the Deal-to-Opportunity mapping phase. If the customer uses multiple Ploomes pipelines, we map each to a separate Twenty pipeline.

Ploomes Products (with Groups and Parts hierarchy) are exported and mapped to Twenty as standard custom objects representing product catalog entries. Product name, SKU (hs_sku equivalent), description, unit price, and group assignments transfer. Because Twenty does not have a native product catalog object by default, we create a Products custom object with the relevant fields before import and link it to Opportunities via a custom lookup field.

Ploomes Quote records map to a Quotes custom object in Twenty, linked to the parent Opportunity. Quote headers, line items (product references, quantities, unit prices), totals, and approval status transfer as custom fields on the Quote record. Note that Ploomes Quote version history is not accessible via the public API, so only the current state of each Quote migrates. We alert customers to this limitation during scoping and recommend exporting PDF snapshots of quote history before the migration window.

Ploomes Tasks linked to Contacts or Deals map to Twenty Tasks. Task title, due date, owner, completion status, and task type transfer. Because Ploomes API pagination is capped at 300 records, we chunk Task extraction into page-based loops across the full dataset. Task assignment resolves by matching Ploomes owner email to the Twenty User email established during the owner reconciliation phase.

Ploomes Users (team members with roles) map to Twenty Users. We extract user name, email, role, and team assignments. Email address is the dedupe and match key. Users must be provisioned in Twenty before any record import that references an Owner field. If the customer has inactive or departed Ploomes users referenced on historical records, we map them to inactive Twenty users to preserve attribution without granting login access.

Ploomes Teams group Users for task assignment and permission scoping. We preserve team structure and team membership during import. Teams in Twenty must be created before users are mapped to them, so we run Team extraction and creation before the User import phase.

Ploomes flat tagging system applied across Contacts, Deals, and Companies maps to Twenty Tags. Tag names and their associations to each record type transfer. Tags in Twenty are applied post-import through a tag association import phase that runs after all primary record types are in place. If the customer has a large volume of tagged records, we run the tag association batch after the base record import is validated.

Ploomes custom fields created via POST /Fields map to Twenty custom fields created through the application settings interface. We export all custom field definitions (name, type, required flag, visibility rules) during discovery, then create the corresponding fields in Twenty before the data import phase begins. Field type mapping is applied: Ploomes text fields map to Twenty text, number fields to number, date fields to date, and checkbox fields to boolean. Conditional visibility rules and duplicate detection settings are documented for manual reconfiguration in Twenty.

Ploomes file attachments linked to Contacts, Deals, or Quotes are stored separately and require separate API calls per object. Twenty's CSV import documentation explicitly states that file attachments are not included in CSV exports and must be re-uploaded manually, migrated via API, or handled through the migration partner. We export attachment metadata (file name, linked record, file type, upload date) into a manifest CSV, then flag this as a manual step for the customer to re-upload via Twenty's file upload interface or API after cutover.