Migrate from Basic Online CRM to Freshsales

Basic Online CRM Contact records map 1:1 to Freshsales Contact. We extract name, email, phone, address, and any custom field values as strings. The Freshsales Contact record is created first so that subsequent Deal imports can resolve the Contact lookup by name or email. If Basic Online CRM records include any lead-stage designation (prospect, qualified), we map those to Freshsales Lead records during scoping based on customer input on whether the destination should use Freshsales Leads as a separate object.

Basic Online CRM Companies map to Freshsales Account. Companies are a flat list without hierarchy, so we import by name match and flag duplicates where the same company name appears multiple times in the export. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert.

Basic Online CRM Deals map to Freshsales Deal. Basic Online CRM exports Deals with linked Contact referenced by an internal numeric ID, not name or email. We run a dual export of Contacts and Deals, cross-reference the IDs during the mapping phase, and recreate the association in Freshsales by matching Contact name to the Contact record created in the prior import phase. If a Deal references a deleted Contact in Basic Online CRM, we flag it as an orphaned Deal for customer resolution before write-back.

Basic Online CRM's pipeline stages are simple text labels. We map each stage name to a corresponding Freshsales Deal stage. If Basic Online CRM has more than the default five stages, we configure additional stages in Freshsales before migration. Stage probability percentages are not tracked in Basic Online CRM, so we set default probabilities matching Freshsales standard stage values unless the customer specifies custom values.

Basic Online CRM Notes are free-text, untyped entries with no timestamp enforcement. We migrate them as Freshsales Notes linked to the parent Contact or Account record. Any timestamp that was explicitly set in Basic Online CRM is preserved; notes without timestamps are assigned the import date as a fallback. Notes are imported after parent Contact and Account records exist so that the lookup relationship is satisfied.

If the Basic Online CRM instance contains task records (simple title-and-status items with no due-date enforcement), we migrate them as Freshsales Tasks. Basic Online CRM does not surface assignee fields on tasks, so we ask the customer upfront which team member should own migrated tasks in Freshsales and apply bulk owner assignment during write-back.

Basic Online CRM custom fields exist but are not typed — all values export as plain strings regardless of intended type (date, number, dropdown). We migrate custom field values as-is to Freshsales custom fields, but we ask customers to confirm intended data types before Freshsales schema creation. Date fields exported in conflicting formats (e.g., Jan 15 2024 vs 15/01/2024) are flagged for manual review before the final import batch.

Basic Online CRM has a basic user concept but no explicit owner assignment on records. We extract every user referenced in the export and match by name or email against the Freshsales destination account's user list. Users without a matching Freshsales account go to a reconciliation queue for the customer's admin to provision before record import. We ask customers which Contact should be assigned as Owner in Freshsales for all records that lack an owner in the source.