Migrate from Comet Suite to Zoho CRM

Comet Suite contacts split by activity type: contacts with recent service visits and a client flag land as Zoho Contacts linked to an Account; contacts without an associated company or with only location-check data route to Zoho Leads. The split rule is applied based on whether the contact has a primary company assignment in Comet Suite.

Comet Suite company records map directly to Zoho Accounts. The company name, domain, industry, and employee count fields translate to Account Name, Website, Industry, and Employee Count respectively. Comet Suite multi-location company records are stored as separate Account Address fields in Zoho.

Comet Suite service records have no direct Zoho CRM equivalent. The record maps to a Zoho Deal (Potential) with a custom pick-list field Service_Type__c capturing the Comet Suite service category, and a multi-line text field Service_Notes__c preserving Comet Suite visit notes, time punches, and GPS coordinates. The Deal Name defaults to the associated account name plus the service date.

Comet Suite visit logs and call records migrate to Zoho Tasks (for completed activities without a specific time) or Events (for scheduled visits with start/end times). The original Comet Suite timestamp, duration, and outcome notes map to Zoho Subject, due date, and description fields. Owner is resolved by email match against Zoho users.

Comet Suite employee time punches represent clock-in/clock-out events. These migrate as Zoho Tasks with a custom field Time_Punch__c storing the raw punch timestamp and a pick-list Status__c indicating IN or OUT. The task is linked to the employee contact record in Zoho for payroll reference.

Comet Suite notes attached to contacts, companies, or service records migrate as Zoho Notes. Rich-text formatting is preserved where the source format is compatible. Notes linked to a service record retain a reference to the migrated Deal in Zoho. Additionally, any images or attachments referenced in the note content are preserved as linked Zoho attachments, and the note's creation timestamp maps to the Created_Time field to maintain audit history.

Files attached to Comet Suite service records and contacts are downloaded and re-uploaded to Zoho CRM. They attach to the corresponding migrated record (Contact, Account, or Deal). Zoho's 25 GB storage limit on Standard plans applies; large file batches may require storage planning.

Comet Suite employee records are matched to Zoho Users by email address. Unmatched employees are flagged and assigned to a fallback Zoho user before migration commits. The Comet Suite employee ID is preserved in a custom field Employee_ID__c on the Zoho User for traceability.

Comet Suite GPS coordinates stored per service record are migrated as custom latitude and longitude number fields on the Deal (Location_Lat__c, Location_Lng__c). Zoho CRM has no native map view for Deal locations — these fields serve as data reference only, not as a route-optimization layer.

Comet Suite custom fields on any object migrate to Zoho custom fields created during the pre-migration schema setup phase. Field data types are mapped: text to text, pick-list to pick-list, date to date, number to number. Zoho field API names follow the module prefix convention (e.g., Leads.Custom_Field__c).

Comet Suite workflow rules governing field-service escalation, notification routing, and status triggers do not have a Zoho equivalent that migrates automatically. We export the workflow definitions from Comet Suite as a structured document for your Zoho admin to reference during Blueprint setup. Revenue-impacting workflows should be rebuilt first.

Comet Suite reports built on service-record data cannot be transferred to Zoho CRM. The underlying data (service history, time punches, visit logs) migrates to Zoho Deals and Tasks, allowing you to rebuild equivalent reports in Zoho Analytics using the migrated fields. We provide a field-mapping document to aid report reconstruction.