Migrate from SuiteDash to Freshsales

SuiteDash Contacts with an assigned lifecycle or status map to Freshsales Lead if unqualified or to Freshsales Contact if associated with a Company record. We evaluate each Contact's status and company association during transform to determine the split. Engagement history (calls, emails, meetings, tasks) attached to each Contact migrates as Freshsales Tasks and Events linked to the resolved Lead or Contact record. Custom fields at the Contact scope map directly to Freshsales Contact custom fields with type matching.

SuiteDash Company records map to Freshsales Account. The Company domain name serves as the dedupe key during import. Primary Contact assignment from SuiteDash migrates as the primary contact lookup on Freshsales Account. Custom fields at the Company Public scope map to Freshsales Account custom fields; Company Private scope fields have no Freshsales equivalent and are flagged for manual disposition (stored as internal notes or rebuilt as a private Note attached to the Account record).

SuiteDash Deals map to Freshsales Deal with dealstage, probability, and pipeline assignment preserved. Closed-Won and Closed-Lost statuses from SuiteDash map directly to Freshsales Deal status values. Custom pipeline stages migrate as Freshsales Deal stages within the configured pipeline. Owner assignment migrates by resolving SuiteDash staff email to the provisioned Freshsales User.

Each SuiteDash pipeline stage becomes a Freshsales Deal stage within a corresponding Freshsales pipeline configuration. Stage probability percentages transfer to Freshsales stage probability values. We configure the Freshsales pipeline schema before any Deal records are imported so that stage assignment is valid at insert time.

SuiteDash Project records have no native Freshsales equivalent and are migrated as a Freshsales custom object named Project. We pre-create the Project custom object schema in Freshsales including custom fields for all SuiteDash Project-level fields, and we store the task hierarchy as a structured JSON field for reference. Project status workflows from SuiteDash map to Freshsales custom picklist values. Active project task assignments (linking tasks to Contacts or Companies) are preserved as notes or as records in a separate Task custom object.

SuiteDash Support Tickets map to Freshsales Case when the destination account includes Service Cloud or when Cases are enabled. Ticket status maps to Freshsales Case Status; ticket priority maps to Case Priority. Conversation threads and attachments migrate as Case Conversations and Case Attachments. SLA configuration on SuiteDash Tickets does not have a Freshsales equivalent and is documented in the post-migration handoff for manual rebuild in Freshsales Case Assignment Rules.

SuiteDash Invoice records migrate as a Freshsales Invoice custom object. Line items, payment status, and Invoice Custom Fields transfer to the custom object schema we pre-create in Freshsales. Historical paid invoices migrate as records only. Active or pending invoice workflows (automated payment reminders, status triggers) do not migrate; we document them in the Automation Audit Report for the customer's admin to rebuild in Freshsales Workflows.

SuiteDash Appointment records have no native Freshsales equivalent and are migrated as Freshsales Task records (for the appointment metadata) or Event records (for calendar-facing scheduling data). Associated Contacts and Companies resolve to Freshsales Contact and Account lookups. Bidirectional calendar sync settings from SuiteDash do not transfer; we flag them for manual reconfiguration in Freshsales calendar settings. Booking page configurations are documented for manual rebuild.

SuiteDash Staff Members who require CRM access migrate to Freshsales User records. Staff records are resolved by email match against the Freshsales User table. Staff Members who do not require CRM access (e.g., support-only staff) are migrated as Contacts rather than Users. Role assignments and staff-level custom fields are preserved as User custom fields or documented for manual role assignment in Freshsales Profiles and Permission Sets.

SuiteDash Tags on Contacts and Companies export as a comma-separated list and map to the Freshsales Tag field on Contact and Account records. We preserve the full tag set for each record during transform so that segmentation logic carries over. The customer chooses whether to use Freshsales Tags or a multi-select custom field for tag-based segmentation during scoping.