Migrate from SprintHub to Freshsales

SprintHub Lead records map to Freshsales Lead. We extract standard Lead fields (name, contact info, status, owner assignment) from SprintHub's GraphQL-style API and insert into Freshsales using the Leads API endpoint. Tags attached to SprintHub Leads migrate as a multi-select text field or to Freshsales's native Tags feature if the destination plan supports it. Lead status values from SprintHub are preserved explicitly rather than assumed to match Freshsales defaults.

SprintHub Contact records map to Freshsales Contact. Contact details, custom properties, and company associations transfer directly. We resolve SprintHub's company association to the Freshsales Account record (created first to satisfy the lookup). Tag associations on Contact records migrate to Freshsales Contact tags, maintaining the color metadata where the destination supports it.

SprintHub Company records map to Freshsales Account. Company name, industry, size, and custom fields transfer without transformation. The Account record is imported before Contact records to satisfy the lookup dependency. We use company name as the dedupe key during import to prevent duplicate Accounts from being created if multiple Contacts reference the same Company.

SprintHub pipeline definitions map to Freshsales Deal structure. Each SprintHub pipeline becomes a Freshsales Deal with its stage names explicitly mapped because they vary per-instance. We extract pipeline configuration as key-value pairs (pipeline name, stage names, stage order) and configure Freshsales Deal stages to match before any Deal records are imported.

Stage names, stage order, and probability percentages from SprintHub map to Freshsales Deal stages. We extract stage configurations as explicit field mappings rather than relying on default stage names. If SprintHub uses stage names that do not match Freshsales defaults (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost), we create custom stage values in Freshsales before Deal import begins.

Tags are global across the SprintHub instance and attach to Leads, Contacts, and other objects. We retrieve the full tag list including color metadata and preserve tag associations on each record during migration. Tags migrate to Freshsales's Tags feature, which is available on all paid Freshsales plans and can be applied to Leads, Contacts, Accounts, and Deals.

SprintHub's WhatsApp multi-account feature is a core differentiator for Brazilian teams managing client-facing and internal numbers. Freshsales standalone does not include WhatsApp; Freshsales Suite includes Freshchat with WhatsApp channel support on the Estate and Forest tiers. We preserve conversation thread metadata (timestamp, participant, account assignment) as activity notes linked to the relevant Contact or Account record. Channel routing rules (which WhatsApp account maps to which team) are documented for manual rebuild in Freshsales Freshchat.

SprintHub custom field names, types, and picklist options vary per instance. We extract the full custom field schema alongside record values during discovery and pre-create equivalent custom fields in Freshsales before data import. Type conversions are applied where needed (for example, SprintHub date formats mapped to Freshsales date fields, multi-select text fields mapped to Freshsales multi-select picklists). Custom field definitions are documented separately for the customer's admin to validate after migration.