Migrate from SprintHub to Salesforce Sales Cloud

SprintHub Lead records map directly to Salesforce Lead. We resolve field names during the API discovery phase (since SprintHub's schema is not publicly indexed), then map SprintHub's lead status, source, owner, and custom fields to Salesforce standard and custom Lead fields. Any SprintHub tags attached to Leads migrate as a multi-select picklist or to custom text fields depending on tag volume.

SprintHub Contact records map to Salesforce Contact. The Contact's associated Company maps to Salesforce Account via AccountId lookup. We preserve SprintHub's contact status, custom properties, and tag associations. Contact records require a resolved AccountId before insert, so Accounts migrate first in the dependency order.

SprintHub Company records map to Salesforce Account. Company name becomes Account Name, industry and size fields map to standard Salesforce Account fields, and custom fields migrate to typed Account custom fields. Company is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert.

SprintHub Pipeline definitions vary per instance and are extracted as explicit key-value pairs. Each SprintHub Pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage order, names, and win/loss probabilities are preserved as Salesforce StageName values and StageProbability percentages.

Stage names, order, and probability percentages migrate from SprintHub to Salesforce Opportunity Stage. We extract stage configurations as explicit mappings rather than assuming standard names, since SprintHub instances vary. Closed-Lost and Closed-Won stage flags are preserved with corresponding Salesforce probability settings.

SprintHub Deals map to Salesforce Opportunity. The SprintHub dealstage property maps to the appropriate Salesforce StageName via the Pipeline-to-RecordType mapping. We resolve AccountId (from SprintHub Company) and OwnerId (from SprintHub Owner by email match) before Opportunity insert. Closed date, amount, and probability migrate to CloseDate, Amount, and Probability.

SprintHub tags are global across the instance and attach to Leads, Contacts, Companies, and Deals. We retrieve the full tag list including color metadata and preserve tag associations on each record. For migrations with fewer than 150 distinct tags per object, we use Salesforce multi-select picklist fields. For larger tag volumes, we use custom text fields with semicolon-delimited values or a dedicated Tag__c junction object.

SprintHub custom field names, types, and picklist options vary per instance. We extract the full custom field schema alongside record values during API discovery and map each to an equivalent Salesforce custom field with the appropriate type conversion. Picklist fields migrate with their value sets; date fields are normalized to Salesforce date format; text fields preserve character encoding.

SprintHub Owner records (assigned to Leads, Contacts, Companies, Deals) map to Salesforce User records by email match. We extract every distinct Owner referenced across all migrating objects and resolve against the Salesforce destination org's User table. Owners without a matching Salesforce User enter a reconciliation queue for the customer's admin to provision before record import resumes.

SprintHub's WhatsApp multi-account support has no native Salesforce equivalent in Sales Cloud. We export the account list, routing rules, and account-to-team assignments as a structured JSON document and a written inventory. Your admin rebuilds the WhatsApp channel configuration in Salesforce Experience Cloud using WhatsApp Business API, or retains a third-party solution such as a dedicated WhatsApp Business API management tool. Conversation histories migrate as Note records or EmailMessage records depending on format.

SprintHub automation rules (trigger conditions, filter logic, multi-step action sequences) are stored in a proprietary format. We extract workflow definitions as structured JSON including trigger types, conditions, actions, and delays. We do not migrate them as Salesforce Flow or as any executable code. We deliver a written workflow inventory with each SprintHub automation mapped to a recommended Salesforce Flow alternative, and the customer's admin or a Salesforce partner rebuilds them post-migration.

SprintHub social media campaign data including campaign name, status, start and end dates, and available performance metrics migrate to Salesforce Campaign. Attribution settings, UTM parameters, and multi-touch journey data do not migrate as these are platform-specific; we document the available SprintHub metrics and flag which are migratable to Salesforce Campaign fields versus requiring a BI tool for reporting.

SprintHub email engagement history migrates to Salesforce EmailMessage records (the email content and headers) linked to a Task record (the activity timeline entry). The WhoId on Task points to the resolved Lead or Contact; WhatId points to the related Opportunity, Account, or Campaign. We use the Salesforce Bulk API 2.0 for large engagement volumes with parent-record lookup resolution.

SprintHub call engagement records map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any recording URL migrate to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original SprintHub timestamp. We resolve the parent WhoId and WhatId at migration time.

SprintHub meeting engagements map to Salesforce Event. StartDateTime, EndDateTime, Location, and subject migrate directly. Attendee records link to EventRelation records pointing at the resolved Leads, Contacts, and Users. Activity ordering is preserved by timestamp.

SprintHub Note engagements migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body migrates as plain text with any embedded image references preserved as external URLs or migrated as separate ContentDocument records.

SprintHub Task engagements map to Salesforce Task. Status, Priority, ActivityDate, and subject migrate directly. Task assignment migrates by resolving SprintHub owner references to Salesforce OwnerId via the User mapping. Any SprintHub custom task fields map to Salesforce custom Task fields.

SprintHub custom objects migrate to Salesforce custom objects with equivalent API names (appended with __c per Salesforce convention). We pre-create the destination schema including all custom fields, field types, picklist value sets, and lookup relationships to standard objects before any data import. Lookup dependencies are resolved at migration time against the parent record's Salesforce ID.