Migrate from Composity CRM to Freshsales

Composity Accounts map directly to Freshsales Accounts. Standard fields (account name, industry, website, address, phone) migrate 1:1. Custom fields defined in Composity's Custom Data module are reverse-engineered at scoping and mapped to equivalent Freshsales custom fields of the matching data type. Account-Contact relationships are preserved via Freshsales' Contact-Account lookup.

Composity Contacts map to Freshsales Contacts with name, email, phone, job title, and address preserved. The Account-Contact relationship resolves via the AccountId lookup after Account records are inserted first. Any custom contact fields migrate to Freshsales custom fields on the Contact object.

Composity Leads from the Campaign & Lead Management module map to Freshsales Leads. Lead status, source, and qualification data migrate to Freshsales Lead Status and custom lead score fields. Composity's lead-to-Contact conversion rules require manual configuration by the customer's Freshsales admin post-migration because Composity's lead qualification stages do not have a direct Freshsales analog.

Composity Deals map to Freshsales Deals with deal name, value, stage, expected close date, and owner preserved. Composity's custom pipeline stages require explicit mapping to Freshsales pipeline stages and stage values during scoping. We configure Freshsales pipeline stages and probabilities to match the Composity stage definitions before migration.

Composity Quotes and Sales Orders are mapped to Freshsales Deal records with line items. Because Freshsales does not have a native Quotes object in all plan tiers, we attach line item data as custom fields on the Deal or as a structured note, depending on the destination plan. Customer should verify whether Freshsales Quotes is available on their selected plan during scoping.

Composity Products (name, SKU, price, description) map to Freshsales Products. We preserve the product-to-quote and product-to-invoice associations where the destination plan supports them. Custom pricing rules stored in Composity's product schema require a pricing field mapping review during scoping.

Composity Projects (available on Growth and Professional plans) have no direct Freshsales equivalent. We extract project name, status, dates, and assigned resources and map them to a Freshsales custom object (if the destination plan supports custom objects) or to Deal records scoped to a project-type pipeline. Custom project fields require explicit schema design during scoping.

Composity Production module records (production orders, BOM references, manufacturing data) have no equivalent in Freshsales CRM. We document production record counts and schema during discovery and deliver a written gap assessment. The customer decides whether to exclude production data or provision a third-party production management tool alongside Freshsales.

Composity activities linked to Contacts and Accounts map to Freshsales Activities of the corresponding type. We preserve activity type, date, description, duration (for calls), and the linked record reference. Activity export from Composity depends on whether the customer enabled activity tracking and whether data exists in the activity log.

Composity Document Storage exports files one at a time. We build a file inventory during discovery, download files in parallel where possible, and reattach them to the corresponding Freshsales Account, Contact, or Deal records using filename or metadata matching. Large document sets require additional time for individual file handling.