Migrate from PromoXcrm to Twenty CRM

PromoXcrm Lead records map to Twenty People. The promo-industry stage labels (Quote Sent, Artwork Approved, Order Confirmed) from the PromoXcrm pipeline become Opportunity stage values in Twenty. We preserve the PromoXcrm Lead source and any lead-score custom properties as custom fields on the Twenty People record. Owner resolution is by email match against Twenty Members.

PromoXcrm Client records carry both person and organization data in a single object. We split these into Twenty People (for individual contact fields: name, email, phone) and Twenty Company (for organization fields: company name, domain, industry). If a PromoXcrm Client has no associated organization, the record migrates as a standalone People record. We use the PromoXcrm client company name as the dedupe key for Company creation.

PromoXcrm pipelines with custom stage names adapted to the promo order lifecycle (Quote Sent, Artwork Approved, Order Confirmed, Shipped) map to Twenty Opportunity records with custom stage picklist values. We create the stage values in Twenty Settings before import and map each PromoXcrm pipeline to a distinct Opportunity record type if the customer uses multiple pipelines for different product lines.

PromoXcrm Projects represent individual promo orders or campaigns tied to a Client. We map Projects to Twenty Opportunity when the Project tracks a deal with a value and stage progression. If the PromoXcrm Project tracks a campaign or job without a sales value (internal project management), we map it to a Custom Object named Project in Twenty's Settings Data Model. The customer chooses the strategy during scoping. Project-to-Client associations migrate as Opportunity-Company or Custom Object lookup relationships.

PromoXcrm Task records migrate to Twenty Task with assignee, due date, status, and description preserved. Automated task-creation rules (trigger-based tasks tied to promo order stages) do not transfer; we document all active automation rules during discovery and provide a written rebuild guide for the customer's admin. Historical completed tasks migrate as records only.

PromoXcrm Commission Records are a promo-industry-specific object with no Twenty equivalent. We export these as structured rows (rep name, order reference, commission amount, percentage, payout date) and document the exact custom fields to create in Twenty Settings Data Model: text field for rep name, currency field for amount, percentage field for commission rate, and date field for payout. The customer creates the schema before import; we provide the CSV with correct column headers.

PromoXcrm Presentation files are internal or client-facing sales assets stored within the CRM. We export available file references (file names, URLs, associated Client or Project) as structured records and re-link them post-migration. Actual file hosting transfer depends on where PromoXcrm stores the files; if they are hosted externally, we provide the reference list for the customer to upload to Twenty's file storage or a linked cloud drive.

PromoXcrm supports custom objects accessible via web-service API. We query the custom object schemas during discovery, export all accessible records, and document the exact custom object and field creation steps in Twenty Settings Data Model. Twenty's auto-generated API means the migrated custom objects are immediately accessible via REST and GraphQL after creation. This is a key advantage of the migration: PromoXcrm's undocumented API access becomes Twenty's fully documented API.

PromoXcrm Owner records (sales reps, admins) map to Twenty Members. We resolve by email match. PromoXcrm does not expose a user list via documented API, so we extract distinct owner references from the Client, Project, and Task records during data audit. Any PromoXcrm owner without a matching Twenty Member goes to a reconciliation queue for the customer's admin to provision before record import.

PromoXcrm's reporting system generates analytics from live data. Saved reports and dashboard configurations are not exportable as standalone objects. We export the underlying data (pipeline values, task status, client records) as structured CSVs so the customer can rebuild reports in Twenty's reporting interface or connect to an external BI tool. This is documented separately as a post-migration configuration task.