Migrate from Intrix CRM to Freshsales

Intrix Client records map directly to Freshsales Account. Client name, industry, address, phone, and website fields migrate to their Freshsales Account equivalents. Email addresses on the Client record (when present as primary contact) map to the Account's primary email. We use the Client record's unique ID as a reference anchor for resolving Contact parent relationships during import.

Intrix Contact records migrate to Freshsales Contact with the parent Account resolved via Client ID or name matching. First name, last name, email, phone, title, and address fields transfer directly. Custom fields on Contact migrate to Freshsales Contact custom properties. The Contact-Client relationship is preserved by resolving the AccountId on Freshsales Contact after Account import is complete.

Intrix Opportunities map to Freshsales Deals. Deal name, amount, expected close date, stage, and owner assignment migrate directly. Intrix custom stage names (customer-configured pipeline stages) require a stage mapping table that we extract from the source account's active pipeline configuration and apply to Freshsales during import. Owner assignment resolves by matching Intrix owner email to Freshsales User.

Intrix uses a customer-configurable pipeline stage model with custom stage names and ordering. We extract the full active stage list during scoping and create equivalent Deal Stages in Freshsales, preserving stage probability percentages and stage type (Open, Won, Lost) for reporting consistency.

Intrix Activity records (calls, emails, meetings, tasks) map to Freshsales Tasks and Events. Email activities migrate as Task records with type=Email. Call logs migrate as Task records with subtype=Call and duration preserved. Meeting records migrate as Event records with start and end time. Each activity is linked to the parent Contact or Deal via the resolved relationship ID. Note-style activities migrate as Note records attached to the relevant Contact, Account, or Deal.

Intrix Projects have no direct Freshsales equivalent. During scoping we determine whether the customer's Projects represent sales-driven initiatives (migrate as Deals with task attachments) or delivery-driven work (migrate as a custom Project object requiring destination schema creation). Project name, description, status, and deadline transfer to the chosen destination. Projects with dependencies require the full dependency graph extracted before migration to determine import order.

Intrix Tasks inherit project context and may have predecessor dependencies. We extract the full task dependency graph, sequence imports so parent tasks land before child tasks, and reconstruct the dependency chain in the destination using Freshsales task relationships or a custom dependency field if the Project was migrated as a custom object. Tasks without dependencies migrate independently. Assignment resolves by matching Intrix task owner to Freshsales User by email.

WHR data only exists if the source Intrix account was on Advanced or Unlimited tier. We confirm tier history during scoping before attempting to extract WHR data. WHR records (employee, date, hours, type) migrate to Freshsales custom fields on the Contact object or to a custom Time Entry object if the destination requires it. WHR is tier-gated on the source; Freshsales has no native time-tracking equivalent at any tier.

Intrix custom fields on Clients, Contacts, Opportunities, and Projects migrate to Freshsales custom properties on the equivalent object. Field type mapping converts Intrix field types (text, number, date, dropdown, checkbox) to Freshsales field types. Unsupported field types are flagged with a notes entry so the customer can decide whether to create a workaround custom field or drop the data.