Migrate from crmConnect to Freshsales

crmConnect Contacts migrate to Freshsales Contact records. We use the contact's email address as the dedupe key during import to prevent duplicate Contact creation. If the crmConnect account uses lead records separately from contacts, we map them to Freshsales Lead with a separate import phase. Custom contact properties discovered during the export phase map to Freshsales custom fields of equivalent type (text, number, date, picklist). Note that Freshsales Growth and above support contact scoring via Freddy AI automatically; the legacy crmConnect contact health scoring is not carried forward but replaced by the native Freshsales feature.

crmConnect Company records map to Freshsales Account. The business name becomes Account Name, and domain information becomes the Website field. We resolve the Account record first during migration so that Contact imports can satisfy the Account lookup reference at insert time rather than post-import lookup reconciliation.

crmConnect Pipelines (available on Professional tier, limited to 1 pipeline) map to Freshsales Deal Pipelines. We configure the Freshsales pipeline with stage names matching the crmConnect stage labels during pre-migration setup. Stage probabilities from crmConnect carry forward to Freshsales stage probability percentages. Multiple crmConnect pipelines (if used) map to separate Freshsales pipeline configurations.

crmConnect Opportunities map to Freshsales Deals. The pipeline assignment, stage name, deal amount, expected close date, owner, and associated contact all migrate. We resolve the owner by email against Freshsales User records held in the reconciliation queue. Custom opportunity fields from crmConnect map to Freshsales custom deal fields of matching type.

crmConnect automations use a drag-and-drop builder with no documented export format. We capture automation intent from screenshots and UI metadata where accessible, then deliver a written workflow inventory document listing each automation's trigger, conditions, actions, and recommended Freshsales Workflow equivalent. The customer's admin rebuilds them in Freshsales Workflows post-migration. This is not a code migration; automation logic does not transfer automatically.

crmConnect Calendar records (synced to Google Calendar and Outlook on Professional tier) migrate to Freshsales Tasks and Events. Event times, attendee lists, and linked contact associations transfer. Single calendar on crmConnect Standard maps to the primary Freshsales user's calendar. The calendar sync itself requires re-authentication with Google or Outlook inside Freshsales after migration.

crmConnect Funnels and landing pages are content objects rather than data records. We export funnel structure, page templates, and form field definitions as structured documentation. Freshsales does not host standalone landing pages; we recommend Freshmarketer or a third-party page builder as the replacement. Form field definitions map to Freshsales Web Forms where the customer chooses to use them.

crmConnect membership portals and course enrollments are separate record types treated as custom objects in the migration. We migrate membership status, enrollment dates, and student records to Freshsales Custom Objects with equivalent schema. The customer pre-configures the Custom Object API name and fields in Freshsales before migration so we can map directly. If the destination Freshsales plan supports Custom Objects, they are available from Growth tier upward.

crmConnect contact tagging and list segmentation export as tag-to-contact mappings. We preserve segment membership as Freshsales Tags attached to each Contact record. Tags are a native Freshsales feature on all tiers and appear in the contact timeline and filter views without requiring a separate list object.

crmConnect email campaign templates and send history export as text, HTML, and metadata. We preserve template structure, subject lines, and contact association lists in a structured document. Freshsales email templates can be created manually post-migration using the preserved content. Automation sequences tied to email sends do not migrate and require rebuild in Freshsales Workflows.