Migrate from Salesboom to Freshsales

Salesboom Lead records migrate to Freshsales Lead with full field mapping. The Salesboom Lead object carries standard fields (name, email, phone, company, status, source) plus any custom Lead fields. We resolve each Salesboom custom field against Freshsales field types: text fields map to Freshsales text, date fields to date, picklist fields to dropdown. Custom fields exceeding Freshsales Growth tier limits (5 on Growth, 10 on Blossom) require the customer to upgrade to Garden, Estate, or Forest before those fields are created. Salesboom Lead status values map to Freshsales Lead Status via a static lookup table created during scoping.

Salesboom Accounts map directly to Freshsales Accounts. The Salesboom account name, billing address, shipping address, phone, website, and industry fields transfer as text or typed equivalents. Custom Account fields are mapped using the same type-resolution process applied to Leads. The Freshsales Account ID is created before any Contact import so that the Contact-to-Account association is satisfied at insert time.

Salesboom Contacts attach to Accounts via the Account-Customer relationship and carry name, email, phone, title, and address fields. We preserve the Contact-to-Account association by inserting Accounts first, then resolving the Salesboom Account ID to the Freshsales Account ID before Contact import. Custom Contact fields undergo the same type-matching process as custom Account fields. Salesboom does not separate Leads from Contacts as distinct objects with a Convert step, so all imported Contacts retain their original record creation timestamps.

Salesboom Opportunities map to Freshsales Deals. The Opportunity name, amount, close date, stage, probability, and owner migrate directly. Stage names in Salesboom do not automatically match Freshsales pipeline stage names; we build a stage-mapping table during scoping that maps each Salesboom stage label to the equivalent Freshsales pipeline stage, with custom stages created in Freshsales if no match exists. Owner resolution is by email match against Freshsales User records.

Salesboom Tasks and Calendar Events are separate objects; both map to Freshsales Task records. We flatten Salesboom task subject, status (open/closed), priority, due date, assigned owner, and related parent object into Freshsales Task fields. Recurring Salesboom tasks are expanded into individual Task records with incrementing due dates before import because Freshsales does not support native recurring task records via API import. Parent-object references (what_id) are resolved by matching the Salesboom parent record's unique ID to the newly assigned Freshsales record ID.

Salesboom Notes attach to any parent record and carry body text and ownership. Rich-text formatting in Salesboom Notes is converted to plain text to ensure compatibility with Freshsales Note rendering. Notes are imported after parent records (Lead, Account, Contact, Deal) are in place, and the parent reference is resolved using a lookup table built during the parent-record migration phase. Notes without a resolvable parent are imported with a NULL parent reference and flagged for manual re-association.

Salesboom Cases (ticket-style support records with status, priority, origin, and resolution fields) map to Freshsales Cases. Case status values map via a static table; custom Case fields undergo type-matching. Auto-assignment rules and escalation workflows that exist in Salesboom do not migrate because they are automation constructs rather than data records. Resolution notes from Salesboom Cases transfer as text in the Freshsales Case Description or a custom Case notes field.

Salesboom allows unlimited custom fields on any standard tab with no per-field pricing. Each custom field is mapped individually: text, number, date, checkbox, picklist, and currency types each have a direct Freshsales equivalent. Custom fields exceeding the destination plan's field count limit require the customer to upgrade Freshsales tiers before migration; we flag this during discovery and present the upgrade or field-pruning decision. Fields that reference Salesboom-specific picklist values require a value-mapping table for Freshsales dropdown population.

Salesboom Owner records map to Freshsales User records via email address as the dedupe and resolution key. Any Salesboom Owner without a matching Freshsales User by email is placed in a reconciliation queue for the customer's admin to provision the corresponding User account before the main record migration proceeds. Active/inactive status is preserved from Salesboom; inactive owners are imported as inactive Freshsales Users with their records still associated.