Migrate from Comet Suite to Salesforce Sales Cloud

Direct 1:1 map for Comet Suite contact records. Salesforce requires an AccountId for most Contact records — contacts without a primary company in Comet Suite are attached to a default 'Unassigned Accounts' placeholder record, or routed to Salesforce Lead if the source record has no associated company.

Comet Suite contacts with no associated deal history or with a status indicating an unqualified prospect can be routed to Salesforce Lead by configurable rule. This split is defined during the mapping planning phase and requires your Salesforce admin to confirm the Lead record type and Status pick-list values.

Direct 1:1 map for Comet Suite company records. Standard Salesforce Account fields — including Name, Industry, Website, NumberOfEmployees, and AnnualRevenue — map directly from Comet Suite equivalents. Parent-child company hierarchies in Comet Suite translate to the Salesforce ParentId field on Account, preserving organizational structures during the migration.

Comet Suite deals migrate as Salesforce Opportunities. Each Opportunity requires AccountId, Name, Amount, StageName, CloseDate, and OwnerId as core fields. Deal-specific custom properties map to Opportunity custom fields, which must be created with the __c suffix in the destination org before the migration run executes.

Comet Suite pipelines translate into Salesforce Record Types on the Opportunity object, each paired with a named Sales Process. If Comet Suite has three deal pipelines, your Salesforce org needs three Opportunity record types created in Setup before data lands — FlitStack delivers a schema plan specifying which record type maps to which pipeline.

Stage names from each Comet Suite pipeline map to StageName pick-list values scoped by the corresponding Salesforce Sales Process. Probability and forecast category are re-applied per stage using Salesforce's standard stage-history model. Stage-entry timestamps are preserved as custom datetime fields if your reporting requires them.

Comet Suite custom properties on deals require Salesforce custom fields on the Opportunity object with the __c suffix. Fields must be created in Salesforce Setup before migration. FlitStack provides a custom-field creation checklist with field type recommendations based on the source data format — pick-list, text, number, date, or checkbox.

Comet Suite call logs map to Salesforce Tasks with Type='Call'; email logs map to Tasks with Type='Email'; meeting records map to Salesforce Events with original start and end times preserved. All activities retain their original owner and timestamp, and are linked to the migrated Contact or Opportunity by reconstructed WhoId and WhatId values.

Comet Suite file attachments on contacts, companies, or deals are downloaded and re-uploaded to Salesforce Files linked to the migrated record. Salesforce's default file size limit is 25MB per file — files exceeding this are flagged and handled per your instructions.

Comet Suite owner references are resolved by matching the owner's email address against Salesforce User records. Unmatched owners are flagged in the pre-migration audit — your team either provisions them in Salesforce first or reassigns their records to a designated fallback owner before migration runs.

Comet Suite custom objects map 1:1 to Salesforce custom objects with the __c suffix. Custom-object relationships in Comet Suite that use a many-to-many model require Salesforce junction objects — FlitStack surfaces these as a separate mapping step in the migration plan.

Comet Suite notes migrate to Salesforce Notes (ContentNote) attached to the relevant Contact, Account, or Opportunity record. Rich-text formatting is preserved where supported by the source field, and plain-text notes transfer without transformation. All migrated notes retain their original creation timestamp and owner for complete audit trail continuity.