Migrate from Dialytica - Marketing Automation Platform to Freshsales

Dialytica Contacts map 1:1 to Freshsales Contacts. The primary key is the contact's email address or phone number. We preserve Dialytica custom fields as Freshsales custom contact properties, which are configurable from the Growth tier onward. Campaign assignment history (which contacts were in which Call Campaign or SMS Campaign) migrates as a tagged activity log entry on each Contact so the full outreach history is visible in Freshsales's timeline without requiring a separate Campaign object.

Dialytica Call Campaigns have scheduling, targeting rules, script references, and agent assignments that do not have a direct Freshsales equivalent because Freshsales does not use a Campaign object for outbound calling in the same way. We map the campaign's contact list to Freshsales Contacts (tagged with the campaign name as a Contact property), and we document the campaign configuration (script text, schedule, targeting criteria) as a Note attached to a Sales Activity or as a custom Account-level record so the customer's admin can reference it during Freshsales workflow setup.

Dialytica SMS Campaigns and SMS Campaigns are distinct objects. Freshsales logs SMS as Tasks with TaskSubtype = SMS (if Freshsales SMS is enabled) or as Activity Log entries on the Contact record. We map each SMS Campaign's contact list and message template to the corresponding Contacts in Freshsales, and the campaign's sending schedule is documented as a Note for the admin to rebuild as a Freshsales workflow or Freshmarketer sequence.

Dialytica call logs include duration, disposition, agent assignment, timestamp, and AI-evaluated metadata (sentiment, score, or call quality flag). We map these to Freshsales Task records with TaskSubtype = Call, preserving CallDurationInSeconds, CallDisposition, and the original timestamp for timeline ordering. AI-generated metadata (Dialytica's LLM evaluation scores) migrates as custom Task fields where the Freshsales tier supports custom fields, or as a Note attached to the Task if custom fields are not available on the selected tier.

Dialytica QA Reviews store supervisor scorecards tied to specific call records with structured criteria and free-text notes. Freshsales does not have a native QA Review object. We create a Custom Module (available from the Pro tier at ~$39/user/mo) with fields for the evaluated agent, the linked call Task, each scorecard criterion, the overall score, supervisor notes, and the review date. Custom Module creation happens during schema design in the Freshsales sandbox before production migration.

Dialytica SMS Activities record individual message events with delivery status, timestamp, and phone number. We map these to Freshsales Tasks with SMS subtype where the Freshsales SMS channel is enabled, or as Activity Log entries linked to the Contact. Delivery status (sent, delivered, failed) migrates to a custom Task field or to the Activity Log body text. If the customer used Dialytica's campaign-scoped SMS tracking, we group related activities by campaign and tag them against the campaign-documented Note for context.

Dialytica Agent and User accounts export with roles, permissions, and active status. We map each Dialytica user to a Freshsales User by email match. Active status and user role are preserved as Freshsales User properties. Any Dialytica user referenced on a Call Record, QA Review, or SMS Activity without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Dialytica SMS Templates export with body text and merge field placeholders. We migrate template content as Freshsales Email Templates (with SMS body adapted to template format) if the customer uses Freshsales email sequences, or as Notes attached to a designated Template reference Contact or Account. Merge field structures are preserved as variable notation (such as {{first_name}} or {contact.first_name}}) and documented so the customer's admin can map them correctly in Freshsales workflow configuration.

Dialytica call scripts and dial plan logic define agent workflows during outbound calls. These are partially structured in Dialytica and may not expose branching conditions as exportable data. We extract script text and sequence order as a Note attached to the relevant Call Campaign reference record, preserving the content but flagging that branching conditions and dynamic routing logic cannot be replicated without manual rebuild in Freshsales's workflow builder.

Dialytica Payments track transaction records associated with campaigns or contacts, including amounts, statuses, and timestamps. Freshsales does not have a native Payments object. If the customer uses Freshsales Deals (Opportunities), Payments map to Line Items or Product entries on the relevant Opportunity. If the customer does not use Deals, we create a Custom Module (Pro tier) for Payment records linked to the Contact, with fields for amount, payment status, date, and associated campaign reference.