Migrate from Comet Suite to HubSpot

Comet Suite contacts map directly to HubSpot contacts. All standard fields (name, email, phone, job title, address) transfer as-is. The primary company association migrates to HubSpot's company_id link; secondary company links surface as secondary associations. Original create dates and last modified timestamps are preserved on each contact record using custom datetime properties, ensuring historical activity tracking carries over without interruption.

Comet Suite companies map directly to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer as standard HubSpot properties. Physical address, billing address, and phone number fields migrate to their corresponding HubSpot company properties. Parent-child company hierarchies map to HubSpot's parent company ID field, requiring the parent company to migrate first to maintain referential integrity across the hierarchy.

HubSpot's lifecycle_stage is a native contact property with a defined pick-list. If Comet Suite tracks a contact status or customer type field, we map it to lifecycle_stage values (subscriber, lead, MQL, SQL, opportunity, customer). Contacts without a source status land as 'lead' by default. You decide the target lifecycle values during the mapping review.

Comet Suite deals map to HubSpot deals. Deal name, amount, close date, and owner all transfer directly. If Comet Suite uses a deal status or stage field, we map it to HubSpot's dealstage property. Closed-won and closed-lost values are preserved. Owner assignment resolves by email match to HubSpot users.

Each Comet Suite deal stage or status label maps to a corresponding HubSpot dealstage value. If HubSpot does not have the matching stage name, we create it in your portal before the migration runs. Probability and forecast category are reapplied per stage during the migration configuration review.

If Comet Suite organizes deals into multiple named pipelines, each pipeline becomes a separate HubSpot pipeline with its own stage set. We create the pipelines in HubSpot first, then assign deals to the correct pipeline during migration. A single HubSpot pipeline is used if Comet Suite uses one unified deal view.

Comet Suite activity records (calls, emails, meetings, notes) migrate as HubSpot engagements linked to the parent contact. Original timestamps and owner email are preserved. Call type and duration transfer as engagement metadata. Note body content migrates to HubSpot notes with original create dates retained.

Comet Suite owner or user records resolve to HubSpot owners by email address. A lookup runs against your HubSpot user list; any unmatched owner is flagged before migration and assigned to a fallback HubSpot user of your choosing. Owner IDs are stored as Source_Owner_ID__c on each record for audit traceability.

Every Comet Suite custom field requires a matching HubSpot custom property pre-created in your portal. We deliver a schema setup list specifying the property name, HubSpot field type, and pick-list values needed. Date fields, number fields, single-line text, and pick-lists all have HubSpot equivalents. Multi-select pick-lists may require custom implementation depending on your HubSpot subscription tier.

Comet Suite file attachments and documents re-upload to HubSpot's file manager and are linked to the associated contact, company, or deal record. Original file names and create dates are preserved. Files larger than HubSpot's 25 MB per-file limit are flagged for manual handling. Inline images embedded in notes are extracted and rehosted within HubSpot.

If Comet Suite exposes custom objects via its data model, those map 1:1 to HubSpot custom objects. Custom object associations that Comet Suite manages as N:N relationships need junction objects in HubSpot — we surface this in the mapping plan and create the required schema. Association integrity is validated post-migration.

Comet Suite's GPS tracking and geofence data have no native HubSpot equivalent. We migrate the most recent location record as custom number properties on the associated contact or ticket record. Historical location logs migrate as custom note or activity records. These properties do not trigger HubSpot automations.

Comet Suite workflows, triggers, and automations do not migrate to HubSpot. We export your Comet Suite workflow definitions as a structured rebuild reference for your HubSpot admin. HubSpot workflows must be constructed in HubSpot's Automation section using triggers, filters, and actions. We do not charge for workflow documentation but rebuilding is a separate service.

Comet Suite reports and dashboards cannot be exported and replayed in HubSpot because they reference Comet Suite-specific field names and calculations. The underlying data (contacts, companies, deals, activities) migrates in full, and HubSpot's analytics tools use that data to build equivalent reports. We validate that all migrated fields appear in HubSpot's property picker so your team can rebuild reports without missing fields.

Comet Suite integrations with third-party tools (payment processors, accounting software, telephony systems) do not migrate. Each integration must be reconnected in HubSpot via the App Marketplace or custom API integration. We document your existing Comet Suite integrations so your team can identify which HubSpot alternatives or native connections to set up post-migration.