Migrate from Composity CRM to Pipedrive

Composity's single Account object stores both company-level data (address, industry, website) and individual contact data (contact name, email, phone). We split this into Pipedrive Organization (company fields) and Person (individual fields) during migration. The original Account ID is preserved in a custom field on the Organization for relationship audit. Any Person record gets a lookup to its parent Organization using domain-based matching on the Account's website field.

Composity Contacts link to Accounts and include name, email, phone, and role. We migrate Contacts as Pipedrive Person records with the role or title stored in a custom field if Pipedrive's built-in label fields are insufficient. The Person-Organization link is resolved using the domain-matching logic from the Account split above.

Composity Leads from the Campaign & Lead Management module map directly to Pipedrive Leads. Lead status, source, and qualification data from Composity map to Pipedrive Lead title, owner, and label fields. Pipedrive's Lead object shares the same custom field schema as Deals, so any Composity custom fields on Leads are created as matching Pipedrive custom fields before migration.

Composity Opportunities (deals) map to Pipedrive Deals. Deal name, value, expected close date, and owner migrate directly. The stage mapping is custom per organization because Composity allows free-form stage names; we extract the full Composity stage definition during discovery and configure matching Pipedrive pipeline stages before migration begins.

Composity pipeline stages are user-defined per tenant with custom names, order, and win/loss flags. We export the full stage definition and recreate it in Pipedrive's pipeline builder before Deal migration. Stage probability weights map from Composity to Pipedrive's probability field per stage. Multiple Composity pipelines map to multiple Pipedrive pipelines (Growth and above).

Composity Invoices from the Sales module include line items, tax codes, payment status, and totals. We map invoice header data (invoice number, date, total, balance due) to custom fields on the associated Pipedrive Deal. Partially paid invoices require balance carry-forward handling documented in the reconciliation report. Full invoice PDFs are attached as Deal files. Pipedrive does not have a native invoice object in its core CRM; we flag this gap explicitly and the customer decides whether to use Pipedrive's invoicing add-on post-migration.

Composity Product catalog entries (name, SKU, price, description) map to Pipedrive Products. Standard Price Book entries are created in Pipedrive during migration. Custom pricing rules in Composity's product schema are mapped to Pipedrive's product pricing fields or stored as custom fields. Product-to-quote and product-to-invoice associations are preserved as deal-product links.

Composity Projects (Growth and above) store project name, status, dates, and assigned resources. Pipedrive does not have a native project management object in core CRM. We map project metadata to custom fields on the related Deal, or if the customer uses Pipedrive's Projects feature (Growth and above), we map to Pipedrive Projects with the project status and dates preserved. Milestone definitions require explicit mapping at scoping and may become deal activity checklists.

Composity's Production module stores manufacturing or job data with BOM references and production order records. Pipedrive has no native production object. We extract production records with BOM references during discovery, then map them to custom fields on the associated Deal or to a Pipedrive custom Object if the customer licenses the required Pipedrive plan. This requires explicit schema design during scoping and is not a standard field-to-field migration.

Composity Inventory records (SKU, quantity, warehouse location, reorder level) map to Pipedrive Products with custom fields carrying inventory-specific data. Quantity discrepancies or negative stock present at migration time are flagged in a pre-migration reconciliation report. Pipedrive's core product model does not include real-time inventory tracking; if the customer requires inventory management post-migration, we recommend a dedicated inventory tool or Pipedrive's integrations with platforms like Sortly or DEAR Systems.

Composity documents export as individual files with no bulk download. We build a file inventory during discovery, identify each document's parent record by filename pattern or metadata, and reattach files to the corresponding Pipedrive record (Deal, Person, or Organization) using the import batch. File upload is done via Pipedrive's file attachment API. Documents with no identifiable parent record are attached to the primary Account record as a catch-all and flagged in the reconciliation report.

Composity activity tracking (calls, emails, meetings, notes) logged against Contacts and Accounts maps to Pipedrive Activities. Activity type, date, description, and linked record migrate. Email content migrates as a note attached to the Person or Deal. Meeting and call details migrate as completed activities with type, duration, and description preserved. Pipedrive's Activity object does not support the same rich interaction metadata as some CRMs; we map what exists and flag any truncated fields in the reconciliation report.

Composity custom fields defined in the Custom Data module apply to any object and are discovered by reverse-engineering the field schema during scoping. We generate a custom field mapping table per object, create matching Pipedrive custom fields (with type mapping: text, number, date, checkbox, dropdown) before migration begins, and migrate values as part of the standard record import. Custom field configuration in Pipedrive can be done inline during the import mapping step per Pipedrive's knowledge base.

Composity users with login credentials, roles, and permissions are exported and matched to Pipedrive User records by email address. Owner assignments on Contacts, Accounts, and Deals are preserved as user references. Users without a matching Pipedrive account go to a reconciliation queue for the customer's admin to provision before record import resumes.