Migrate from Constructor to Zoho CRM

Constructor leads migrate directly to Zoho Leads. Zoho Lead fields (Lead Status, Lead Source, Industry) map to equivalent Constructor pick-list values. Unconverted Constructor leads that are already associated with a company land as Zoho Leads — the Account link is preserved as a lookup field.

Constructor contacts map 1:1 to Zoho Contacts. The primary Account link (Constructor's company field) becomes Zoho's Account Name lookup. Contacts without a primary company are attached to a default placeholder Account so Zoho's required AccountId constraint is satisfied during import.

Constructor accounts migrate directly to Zoho Accounts, preserving fields such as name, website, phone, industry, ownership, and address. Parent‑child hierarchies map to Zoho's Account Hierarchy field, so parent accounts are imported first to build the tree. Multi‑account associations on a single contact collapse to a primary AccountId plus the Account Contact Relation secondary link, matching Zoho's 1:N‑to‑N:N model. All custom account fields transfer to Zoho custom fields after schema setup.

Constructor deals map to Zoho Deals directly. Constructor's pipeline and stage pair maps to Zoho's Pipeline and Stage pick-list values via explicit value-by-value mapping since Constructor stage names rarely match Zoho's default stage labels. Amount, close date, and owner transfer as-is.

Constructor call logs and to-do tasks migrate as Zoho Tasks with the Type field set to Call or Task respectively. Subject, Description, Status, and Priority carry over. Original Created Time and Assigned To timestamps are preserved; the Owner resolves by email match to Zoho users.

Constructor meetings and calendar events migrate as Zoho Events. Start DateTime and End DateTime transfer directly. All-day events use Zoho's All-Day Event flag. The WhatId field links the event to the parent Contact, Account, or Deal record using the ID preserved from Constructor's association.

Constructor notes migrate as Zoho Notes with Content (body text) and ParentId linking back to the related record. Rich-text formatting is preserved where the source format is HTML; plain-text notes import cleanly. Note titles default to a truncated excerpt of the note body if Constructor did not store a separate title field.

Constructor file attachments are extracted from records, re-uploaded to Zoho's Attachments module, and linked back to the parent record via the Related To field. Individual file size is capped at 25MB in Zoho — files exceeding this limit are flagged before migration so your team can decide whether to host externally or split the attachment.

Constructor custom objects map 1:1 to Zoho Custom Modules. If the Constructor custom object name contains _C, Zoho's migration wizard auto-creates the module during import; otherwise the module is pre-created in Zoho before data lands. Custom-object relationships that are many-to-many in Constructor map to Zoho's linking modules or related-list lookups depending on the relationship cardinality.

Constructor owner IDs resolve to Zoho users by email address match. Unmatched owners are flagged before migration — your team either creates the Zoho user first or assigns those records to a fallback owner. This is a prerequisite step that must complete before any module migration runs because Zoho requires a valid OwnerId on all owned records.

Constructor workflows and automation rules do not migrate. FlitStack exports your Constructor workflow definitions as a structured JSON document and a written description of each rule's trigger, condition, and action so your Zoho admin or implementation partner has a rebuild reference. Workflows must be manually reconstructed in Zoho Blueprint or Deluge after the data migration completes.

Constructor reports and dashboards are not migrated — the underlying data comes over but the report definitions, chart configurations, and scheduled delivery settings are destination-side configuration. FlitStack documents which records feed each Constructor report so the rebuilding admin knows which Zoho Reports or Analytics modules to rebuild and which Zoho custom fields the reports should reference.

Constructor's third-party integrations (Outlook sync, Gmail plugins, Zapier connections, accounting connectors) do not migrate. Each integration must be rebuilt in Zoho or reconnected to the new CRM using Zoho's connector library, Zoho Flow, or the same third-party middleware your team already uses. FlitStack lists every active integration found during discovery so none are forgotten at cutover.

Constructor stores relationship labels and tags on contacts and deals that have no built-in Zoho equivalent. These migrate as custom pick-list or multi-select fields on the relevant module. You choose the field type in Zoho — single-select for simple tags or multi-select if Constructor stored multiple labels per record. The original Constructor label names are preserved as field values.

Zoho's standard Last Modified Date reflects when the record was changed in Zoho, not when it was last updated in Constructor. We preserve Constructor's last-modified timestamp as a custom datetime field so reporting shows the original modification history. This is essential for teams whose SLA metrics or sales-cycle reporting depend on the source system's modification dates.