Migrate from noCRM.io to Freshsales

noCRM Leads map to Freshsales Lead if the lead has not yet entered a qualification process, or to Freshsales Contact if the Lead has a status indicating it is sales-qualified. We extract the lead status, pipeline step, and any custom status fields to determine the split at migration time. Won leads from noCRM become Freshsales Contacts attached to Accounts with a corresponding Deal. Lost and Cancelled leads become Freshsales Leads with status set to Closed Lost to preserve the historical record. The original noCRM lead status is preserved in a custom field nocrm_original_status__c on both Lead and Contact for audit trail.

noCRM Pipelines map to Freshsales Pipelines. Each Pipeline's name and stage count are preserved. Starter-tier noCRM accounts (limited to one pipeline) migrate to a single Freshsales pipeline with Stages mapped one-to-one from noCRM Pipeline Steps.

noCRM Pipeline Steps map to Freshsales Stages within the corresponding Pipeline. Step order, name, and any custom color or icon metadata are preserved as Stage metadata. We set the default Stage for new leads based on the first Pipeline Step in noCRM.

noCRM Prospecting Lists migrate to Freshsales Segments as static lists. Each Segment retains the original list name and its member lead IDs, which we resolve to the corresponding Freshsales Lead or Contact record post-split. Segments are rebuilt in Freshsales as manual/static lists rather than dynamic lists because noCRM Prospecting Lists are membership-based, not rule-based.

noCRM Tags are freeform labels applied to Leads. We preserve all tags as-is and map them directly to Freshsales Tags. Freshsales supports tags on Contacts and Accounts. Tags applied to noCRM Leads that split into Freshsales Leads carry over to the Lead record and are not lost during the Contact conversion process.

noCRM Lead comments and activity log entries migrate to Freshsales Notes attached to the corresponding Lead, Contact, or Account record. Each Note preserves the original author, timestamp, and full comment text. Step-transition events (Lead moving between Pipeline Steps) are documented as Note entries with a system-generated note body describing the transition for historical completeness.

noCRM Users are mapped to Freshsales Users by email address. We extract all users referenced on Lead assignment, comments, and Pipeline ownership. Any noCRM User without a matching Freshsales User goes to a reconciliation queue for the customer admin to provision before the main migration phase begins. Role and permission structures are not transferred and must be reconfigured in Freshsales Admin settings post-migration.

noCRM Predefined Fields are account-specific custom lead fields configured under Admin > Sales process > Predefined Fields. We extract the field definitions (name, type, options, required flag) and recreate them as Freshsales custom fields on the Lead or Contact object before record import. Field type mapping follows: text fields to Text, dropdown fields to Picklist, number fields to Number, date fields to Date. Any noCRM custom field without a direct Freshsales equivalent is documented and mapped to a Text field with a note for the admin to validate post-migration.

Files attached to noCRM Leads are exported as binary blobs and reattached to the corresponding Freshsales record (Lead, Contact, or Account). Freshsales CRM storage limits apply; files exceeding the plan storage allowance must be hosted externally with a link stored in the record. We flag any file larger than 25 MB for admin review before migration.