Migrate from Composity CRM to Zoho CRM

Composity Accounts map directly to Zoho CRM Accounts. Standard fields (account name, address, industry, phone, website) transfer as typed Zoho fields. The Account-Contact relationship is preserved so that every Contact carries a reference to its parent Account in Zoho. Custom fields defined in Composity's Custom Data module reverse-engineer during scoping and map to Zoho custom fields on the Accounts module.

Composity Contacts map to Zoho Contacts with full name, email, phone, and role preserved. Composity's account-contact linkage maps to Zoho's Account Name lookup. Custom contact properties from the Custom Data module transfer to Zoho custom fields, and any Composity custom field applied to contacts is mapped individually during the field-level discovery phase.

Composity Leads from the Campaign & Lead Management module map to Zoho Leads. Lead status, source, and qualification data transfer directly. Composity's custom stage labels for leads require an explicit mapping table because both platforms allow user-defined stage names. We export the full Composity stage definition during scoping and configure matching Zoho Lead Status values before import.

Composity Opportunities (handled in the Sales submodule) map to Zoho Deals. Deal name, value, stage, expected close date, and owner transfer directly. Composity stage names are custom per organization and require an explicit stage map at scoping; each Composity stage maps to a Zoho Stage value on the Deal record. Owner assignment resolves by email match to Zoho Users.

Composity's user-defined pipeline stages export as a stage definition list including name, order, and win/loss flags. We configure Zoho Deal Stages to match, recreating the exact stage sequence and probability values. Zoho's Stage field is a picklist rather than a free-text field, so we map Composity's custom stage names to Zoho picklist values before migration.

Composity Quotes map to Zoho Quotes. Quote headers, line items, tax codes, and totals transfer directly. Zoho Quotes link to a Deal via the Deal Name lookup and require a Product record to exist before the quote line item can reference it. We sequence Product import before Quote import to satisfy the lookup dependency.

Composity Sales Orders transfer to Zoho Sales Orders. The order header fields map directly; line items depend on Products being present in Zoho first. Partially fulfilled or backordered sales orders require explicit status mapping because Composity and Zoho use different fulfillment state values.

Composity Invoices from the Sales module map to Zoho Invoices. Invoice headers and line items transfer directly. Partially paid or unpaid invoices require balance carry-forward handling: the remaining balance amount becomes a new open invoice in Zoho rather than closing the original as fully paid. We flag any invoice with payment status other than Paid during scoping.

Composity Product catalog entries (name, SKU, price, description) map to Zoho Products. Product-to-quote and product-to-invoice associations migrate as the Quote and Invoice line items reference the imported Products by name. Custom pricing rules defined in Composity's product schema may require manual field mapping at scoping if they use non-standard field types.

Composity Inventory records (SKU, quantity, warehouse location, reorder level) map to Zoho Inventory items if the destination account includes Zoho Inventory as a module. If Zoho Inventory is not enabled, we map to Zoho Products with a custom inventory flag field. We flag any quantity discrepancies or negative stock present in Composity at scoping because these may require adjustment before import.

Composity Projects (Growth and above) map to Zoho Tasks grouped under a Deal or Account, or to a custom Projects module if the customer chooses to build one. Project name, status, dates, and assigned resources transfer; custom project fields and milestone definitions require explicit field-level mapping at scoping. Milestones map to subtasks or a separate custom Milestone object.

Composity Production module records have no native Zoho CRM equivalent. We design a custom module (e.g., Production_Orders) in Zoho to hold production order data, BOM references, and work order status. This requires schema design during scoping and pre-creation of the custom module fields before any Production data is imported. The BOM (bill of materials) lines map to a related custom object or sub-list within the production order record.