Migrate from Insightly Marketing to Freshsales

Insightly Contact records map to Freshsales Contact. Standard fields (name, email, phone, address, title) migrate directly. We map lifecycle stage to a Freshsales custom Contact property since Freshsales does not have an equivalent native Lifecycle Stage field. Owner assignment (Insightly user to Freshsales user) resolves by email match. Custom fields migrate as Freshsales custom properties after the customer creates them in Freshsales admin settings, which is a pre-import step we coordinate.

Insightly Organization records map to Freshsales Organization (the account object). Organization name, domain, industry, phone, address, and annual revenue migrate directly. Organization-to-Organization relationships migrate as Freshsales custom association records if the customer uses them. Custom organization fields migrate as Freshsales custom Organization properties.

Insightly Lead records map to Freshsales Lead. Lead status, source, rating, and owner assignment migrate directly. Insightly lead scores and any custom lead fields migrate as Freshsales custom Lead fields. Leads in Freshsales can coexist with Contacts from the same migration; the customer decides during scoping whether to merge converted leads or keep them separate for reporting purposes.

Insightly Opportunity records map to Freshsales Deal. Deal name, amount, stage, probability, expected close date, and owner assignment migrate directly. Pipeline names from Insightly map to Freshsales pipeline assignments; if Insightly used multiple pipelines, we consolidate to Freshsales single-pipeline structure and document the original pipeline assignment in a custom Deal field. Custom opportunity fields migrate as Freshsales custom Deal properties.

Insightly Projects do not have a native equivalent in Freshsales CRM. We handle this in one of two ways depending on the customer's scope: either Projects migrate as a custom Freshsales Object (Freshsales Enterprise allows custom objects) with all standard project fields as custom properties, or the project records are decomposed into Freshsales Tasks with a custom Project Name field and milestone tasks grouped by parent-project reference. The approach is chosen during scoping based on Freshsales tier and the customer's reporting needs for project data post-migration.

Insightly Task records map to Freshsales Task. Due date, priority, status, description, and owner assignment migrate directly. The related-to reference (Contact, Organization, Opportunity, or Project) migrates as a Freshsales custom Task property because Freshsales Task does not natively support a polymorphic WhatId equivalent. Task ownership resolves by email match against Freshsales User records.

Insightly Comments (both task-linked and standalone) migrate to Freshsales Note records. Note body content, created date, and owner assignment migrate directly. We link Notes to the parent Contact, Organization, or Deal using Freshsales Note association fields. If Notes contain attachment references, we flag these for manual file re-upload post-migration because Insightly attachment URLs are not portable across platforms.

Insightly Custom Objects require schema discovery before migration because field names, field types, and relationships are unique to each Insightly instance. For Freshsales Enterprise, we create matching custom object schemas in Freshsales before import. For Growth and Pro tiers, we map custom object fields as additional custom properties on the closest standard object (for example, a Project-equivalent custom object with a Contact lookup maps to Freshsales custom fields on Contact with a text reference field). This is a scoping-phase decision based on Freshsales tier.

Insightly custom fields on any standard object (Contacts, Organizations, Opportunities, Projects, Tasks) migrate to Freshsales custom properties on the corresponding object. The customer creates the custom property definitions in Freshsales Admin Settings before migration begins; we provide the exact field name, field type, and sample values during schema discovery so this can be done in advance. We flag any Insightly validation rules that may restrict what values can be imported into Freshsales custom fields of equivalent type.

Insightly Tags on Contacts, Organizations, Opportunities, and Projects migrate to Freshsales Tags. We extract the tag names per record and re-apply them as Freshsales native tags using the Freshsales tag API. If the customer uses tags as a segmentation or scoring mechanism rather than simple labels, we document the tag taxonomy during scoping and flag any tag logic that should be represented as custom fields or Deal properties in Freshsales.