Migrate from Comet Suite to Freshsales

Comet Suite person records split into Freshsales Lead or Contact based on lifecycle stage value. If Comet Suite has a 'status' field marking records as Customer/Active, those land as Freshsales Contact; all others land as Lead. Freshsales Lead object stores pre-conversion records with its own set of custom fields.

Comet Suite company records map 1:1 to Freshsales Account. Account Name, Website, Industry, Phone, Address, Number of Employees, and Annual Revenue fields migrate directly. Parent-child company hierarchies in Comet Suite map to Freshsales Parent Account lookup if the source stores a parent_company_id field, preserving organizational structure.

Comet Suite deal or property records map to Freshsales Deal. Freshsales requires deal_value — if source deal has a null or missing amount field, we apply a configurable default (typically 0) and flag the record in the migration report. Pipeline and stage values map to Freshsales Deal Stages and Sales Flows.

Comet Suite owner IDs are resolved by email match against Freshsales user list. If a Comet Suite owner email has no corresponding Freshsales user, the record is assigned to a fallback owner (configurable) and flagged in the pre-migration owner-resolution report. Active/Forecast_Category fields on the deal are preserved from source.

Comet Suite activity entries (calls, emails, meetings, tasks) migrate as Freshsales Tasks with Type, Subject, Description, and Due Date fields. The original owner assignment is resolved via email match and stored as Freshsales Task owner_id. Original timestamps are preserved in custom datetime fields since Freshsales CreatedDate reflects migration time, not source creation time, ensuring historical accuracy.

Comet Suite notes and record descriptions migrate as Freshsales Note records with title, body, and parent record links (Contact, Account, or Deal). Rich-text formatting is simplified to plain text if the source uses HTML notes, to avoid rendering issues in Freshsales.

If Comet Suite has custom objects beyond standard contacts/companies/deals, we evaluate whether Freshsales Enterprise custom modules can hold them or whether they should be collapsed into custom fields on the parent standard object. Custom module creation is scoped to Enterprise plan; Starter/Growth plans receive custom fields on Lead, Contact, Account, or Deal.

Comet Suite product catalog items map to Freshsales Product records including name, price, cost, and description. Product status (active/inactive) maps to Freshsales Product status. If the source stores product quantities or unit prices on deal records, we migrate those as Freshsales Deal Product records linking the Product to the Deal, or store them in custom fields on the Deal object for further segmentation.

Comet Suite file attachments associated with records re-upload to Freshsales file storage. Freshsales file size limits (typically 25MB per file) apply; files exceeding this are flagged with a download-link reference rather than inline attachment. Inline images in notes are extracted and rehosted.

Comet Suite lifecycle stages, status values, or tag strings map to Freshsales Contact Lifecycle Stage (on Contact) or a custom pick-list field on Lead. We create the pick-list values based on source distinct values and map each record's status to the corresponding Freshsales value. If the source uses multi-value tags, we store them in a pipe-delimited custom text field.

Comet Suite campaign or marketing list records map to Freshsales Campaign with name, status, type, and start/end dates. Campaign member associations from source contacts link to Freshsales Campaign Members. Note: Freshsales campaign features are plan-dependent (Pro+); Starter plans may store campaign data in custom fields.

Comet Suite email threads and communication logs are stored as Notes in Freshsales (with Type='Email') linked to the parent Contact or Deal. The note body contains the thread summary and timestamps. Original message headers are preserved in a custom long-text field if source provides them.

If Comet Suite stores territory or region assignments on records, we map them to Freshsales Territory Management (Pro and Enterprise plans) or store as a custom pick-list field on Account/Contact for Growth plans. Territory assignment rules cannot be migrated and must be reconfigured in Freshsales after migration.