Migrate from Cirqll to Zoho CRM

Cirqll Customers map to Zoho Leads for unqualified prospects and Zoho Contacts attached to Zoho Accounts for qualified buyers. We resolve the split by evaluating Cirqll's lead qualification status field: unqualified status maps to Zoho Lead; qualified or active customer status maps to Zoho Contact with an Account created from the customer's company name. The original Cirqll Customer record ID is preserved in a custom field cirqll_original_id__c on both Lead and Contact for cross-system audit.

Cirqll Lead records map directly to Zoho Lead with owner assignment, source attribution, and qualification status preserved as Zoho Lead Status. The cirqll_lead_status field maps to a Zoho picklist that the customer's admin configures before migration. Any Cirqll custom properties on Lead records migrate to Zoho custom fields created during schema configuration.

Cirqll does not expose a separate Company object in its documented schema, but company information embedded in Customer records maps to Zoho Account. The company name from the Customer record becomes the Account Name, and the customer's city or region becomes the Account City field. Account is created before any Contact import so that the Account Lookup is satisfied at the moment of Contact insert.

Cirqll Task records map to Zoho Tasks with Subject, Due Date, Status, Priority, and Owner preserved. The Task type or category field in Cirqll maps to Zoho's Task Type picklist if configured, otherwise to a custom field cirqll_task_category__c. Completed vs. open status migrates as-is; Zoho Task status values (Not Started, In Progress, Completed) are matched to Cirqll equivalents during field mapping.

Cirqll Activity records — calls, emails, meetings — map to Zoho Tasks (for calls and emails) and Zoho Events (for meetings). Call duration and disposition migrate as custom Task fields. Meeting start and end timestamps migrate to Event Start Time and End Time. Activity owner maps to Zoho User by email resolution. The original Cirqll activity_type field determines whether the record lands as Task or Event.

Cirqll Notes attached to Customers or Leads migrate to Zoho Notes linked via the parent record's Lookup. Note body (rich text) migrates as-is. Note creation timestamp and author attribution are preserved in Zoho Note fields. Notes without a parent record are held in a reconciliation queue and linked to the nearest matched Contact or Lead based on record context.

Cirqll Calendar events migrate to Zoho Events with Subject, Start DateTime, End DateTime, Location, and attendee list preserved. All-day event flags require field-level mapping since Zoho handles all-day flags as a separate Boolean field. Recurrence patterns in Cirqll are documented as-is in a custom field cirqll_recurrence_detail__c because Zoho Event recurrence uses a different schema and admin rebuild is recommended rather than automated parity.

Cirqll document blobs do not export via the standard API and require a separate download-and-reupload pass. We download each document with its original filename and metadata, then upload to Zoho CRM Attachments or Zoho WorkDrive depending on the customer's plan tier. File size, upload timestamp, and parent record association are preserved. Document version history is not carried forward because Cirqll does not expose version metadata via API. This pass runs as a secondary migration phase after all structured records are committed.

Cirqll User accounts referenced as owners on Customer, Lead, Task, and Activity records map to Zoho Users by email match. We resolve owners during the pre-migration owner reconciliation phase. Any Cirqll User without a matching Zoho User is held in a queue for the customer's admin to provision before record import resumes. Active vs. inactive status carries forward; role-based permissions do not transfer because Zoho permission sets are destination-specific.

Cirqll custom fields and extended properties on Customer and Lead records migrate to Zoho custom fields scoped to the relevant module. We create the Zoho custom field schema (field type, picklist values, required vs. optional) during the sandbox migration phase. Text fields map to Zoho Text, numeric properties to Number, date properties to Date, and checkbox properties to Checkbox. The mapping is confirmed against actual Cirqll API responses because full schema documentation is not publicly available.