Migrate your Composity CRM data

Accounts is the core CRM object in Composity's Account & Contact Management module. We migrate Accounts 1:1 with standard fields (name, address, industry, status) and preserve any custom properties defined in the Custom Data module.

Contacts are linked to Accounts and include name, email, phone, and role data. We preserve the Account-Contact relationship during migration and map any custom contact fields to the destination's equivalent properties.

Leads are managed through Composity's Campaign & Lead Management module. We map Lead status, source, and qualification data to the destination's Lead or Contact object, depending on the target system's object model.

Quotes and Opportunities are handled through the Sales submodule. We map deal name, value, stage, and expected close date. Stage names are custom-configurable per organization and require explicit mapping to the destination pipeline.

Pipeline stages are user-defined in Composity's CRM settings. We export the full stage definition including name, order, and win/loss flags and recreate them at the destination during migration.

Invoices are part of the Sales module and include line items, tax codes, payment status, and totals. We map invoice headers and line items directly; partially paid invoices require balance carry-forward logic which we handle explicitly.

Product catalog entries include name, SKU, price, and description. We preserve product-to-quote and product-to-invoice associations. The product schema may include custom pricing rules that require field-level mapping.

Projects is a separate module available in Growth and above. We map project name, status, dates, and assigned resources. Custom project fields and milestone definitions require explicit mapping at scoping time.

Production module data is unique to Composity and has no direct equivalent in most CRMs. We extract production records with their BOM (bill of materials) references and map them to a compatible structure or custom object at the destination.

Inventory is managed in the Inventory module with SKU, quantity, warehouse location, and reorder levels. We map inventory records and flag any quantity discrepancies or negative stock that may exist at migration time.

Documents are stored within Composity's Document Storage module. We export files individually and reattach them to their corresponding records at the destination. File metadata including upload date and author is preserved where the destination schema supports it.

Activity tracking includes calls, emails, meetings, and notes logged against Contacts and Accounts. We map activity type, date, description, and the linked record. Interaction data export depends on whether the source tenant has activity logging enabled.

Custom fields are defined in the Custom Data module and can be applied to any object. We reverse-engineer the custom field schema during discovery and generate field-level mappings for each object that uses them.

Composity users with login credentials, roles, and permissions are exported and mapped to the destination's user records. Owner assignments on Contacts, Accounts, and Deals are preserved as user references where supported.