Migrate from Smarketing Cloud to Freshsales

Smarketing Cloud Contact records map directly to Freshsales Contact. Standard fields (full name, email address, phone number, lifecycle stage) transfer to Freshsales native Contact fields. Custom Contact properties built incrementally in Smarketing Cloud are mapped to Freshsales custom contact fields, which we create in the destination schema before import. The Contact-Company linkage is preserved via foreign key resolution during the import phase.

Smarketing Cloud Company records map to Freshsales Account. The Company-Contact relationship table is exported alongside both objects so that we can reconstruct Account-Contact linkages during import by resolving Contact records to their parent Account via the relationship table. Website, industry, employee count, and address fields map directly where present in the Smarketing Cloud export.

Smarketing Cloud Pipelines and Pipeline Stages are account-specific configurations with freely chosen stage names. We export the full stage sequence and ordering from Smarketing Cloud, then configure matching Freshsales Deal Stages with equivalent probability weights before migration. The customer reviews and approves the stage mapping during scoping so that deal history reflects the correct lifecycle progression in Freshsales.

Smarketing Cloud Deal records map to Freshsales Deal. Deal amount, closing date, owner (resolved via User mapping), associated Contact, and associated Company transfer to Freshsales Deal fields. The pipeline assignment maps to the Freshsales Deal Stage configured in the Pipeline step. Custom Deal properties migrate to Freshsales custom Deal fields.

Smarketing Cloud Marketing Campaigns store member lists and send history. We export Campaign membership records (which Contacts were enrolled in which Campaigns and when) as a custom Deal record type or as Campaign Tag associations in Freshsales, depending on the customer's preference during scoping. The original Campaign name and enrollment timestamp are preserved in custom fields. Active send history is exported as Activity notes if retention limits allow.

Activity logs (calls, emails, meetings, tasks, notes) linked to Contacts and Companies export with activity type, timestamp, owner, and description text. Owner assignment is preserved via email matching to Freshsales User records. Activity timestamps are preserved to maintain the timeline ordering in Freshsales Activity Feeds. Historical data depth is limited by the account's plan tier; we audit available history depth during discovery and scope export to the oldest accessible records.

Smarketing Cloud User records export with name, email, role, and team assignment. We match Smarketing Cloud users to Freshsales users by email address. Inactive users can be exported but migration scope is agreed per engagement. Any User without a matching Freshsales account goes to a reconciliation queue for the customer's admin to provision before record import.

Smarketing Cloud custom object schemas, field definitions, and all record data export via the custom ETL pipeline. Freshsales requires destination schema to be created before import, so we coordinate sequencing so custom objects are provisioned in Freshsales first. Custom field types are mapped to Freshsales field types (text, number, date, picklist, checkbox, etc.) during the schema design phase. Lookup relationships between custom objects and standard objects are preserved via foreign key resolution during import.

Smarketing Cloud Tags on Contacts and Companies export as tag strings per record. We reapply them in Freshsales as tags using Freshsales bulk tag operations, preserving the tagging structure per record. If the customer has used tags for segmentation or scoring, we document the tag taxonomy during scoping for recreation in Freshsales.

Static lists and dynamic segments export as record sets. For static lists, we export the Contact IDs and recreate them as Freshsales Static Groups. For dynamic segments, we document the filter criteria and recommend recreating them as Freshsales Smart Lists or using Freshsales Filters rather than attempting to export dynamic logic, which does not transfer across platforms.