Migrate from LeadSmart Channel Cloud to Freshsales

LeadSmart Lead records migrate 1:1 to Freshsales Lead. The LeadSmart Lead Status field maps to Freshsales Lead Status with a value mapping table built during scoping. Any lead source, industry, or custom fields on LeadSmart Lead objects are inventoried and mapped to Freshsales standard or custom Lead fields. Owner assignment migrates by email match against Freshsales Users.

LeadSmart Contact records map 1:1 to Freshsales Contact. Address, phone, email, title, and custom distributor/manufacturer relationship fields migrate with type mapping applied. LeadSmart's industry-specific custom fields on Contact (e.g., distributor tier, dealer status) are flagged if no Freshsales equivalent exists and offered as custom field creation post-migration.

LeadSmart Account records map to Freshsales Account. LeadSmart uses Account hierarchies to model manufacturer-distributor-dealer relationships; we preserve parent-account hierarchy during migration by resolving Parent_Account lookup references. Website, industry, billing address, and custom fields migrate directly. The Account dedupe key is the account name and domain.

LeadSmart Opportunity records map to Freshsales Deal. StageName maps to Freshsales Deal Stage via a value mapping table. Amount, CloseDate, Probability, and OwnerId migrate directly. Record Type and Sales Process from LeadSmart map to Freshsales pipeline and stage configuration on the Deal object. Closed-Lost and Closed-Won dates are preserved.

LeadSmart Activity records (Tasks and Events) migrate to Freshsales Activity. Task status, priority, due date, and description migrate directly. Call disposition and duration from LeadSmart Tasks map to Freshsales Activity custom fields where configured. Meeting events migrate with start time, duration, and location. Owner assignment resolves by email match against Freshsales Users.

LeadSmart Campaign records migrate to Freshsales Campaign. Campaign Member status history is preserved as Campaign Member records linked to the corresponding Leads or Contacts. Budget, start date, end date, and campaign type migrate directly. Custom marketing automation fields on LeadSmart Campaign require field-level mapping or custom field creation in Freshsales during the migration window.

LeadSmart adds industry-specific custom fields to standard Salesforce objects for distributor and manufacturer workflows. We inventory all custom fields during scoping, map them to Freshsales standard fields where semantic equivalents exist, and flag unmapped fields for custom field creation post-migration. A supplementary CSV export of unmapped field data is delivered alongside the migration for manual import if needed.

LeadSmart Files and Attachments linked to Leads, Contacts, Accounts, and Opportunities migrate as Freshsales File attachments. File content and the parent record linkage (linked_to_type, linked_to_id) are preserved. Large binary attachments (over 10 MB) may require chunked transfer with parent-record resolution verified after each chunk.

LeadSmart User records map to Freshsales Users by email match. Active status, role, and profile assignment migrate where the destination Freshsales plan supports role-based access control. Any LeadSmart User without a matching Freshsales User email goes to a reconciliation queue for the customer's admin to provision before record import resumes.

LeadSmart Partner Portal external partner records linking internal Accounts to channel partners (reps, brokers, dealers, distributors) do not have a native Freshsales equivalent. We map these to Freshsales Account Contact Role linkage records or recommend a custom object (Partner, Channel Partner) that the customer's admin configures post-migration. External user login and permission configurations are documented in the handoff guide rather than migrated.