Migrate from Crust CRM to Freshsales

Crust CRM Contact records map to Freshsales Contact. Standard fields including name, email, phone, and address migrate directly. If Crust CRM uses a lifecycle stage property to track prospect progression, we preserve that value in a Freshsales custom text field and set the Contact's Contact Status to the corresponding Freshsales lifecycle stage value. The company-contact linkage is preserved by resolving the Crust CRM company_id to the Freshsales Account created during the Account phase of migration.

Crust CRM Company records map to Freshsales Account. Domain, industry, annual revenue, employee count, and address fields migrate directly. Crust CRM's company-contact linkage (many contacts per company) maps to Freshsales's standard Account-Contact lookup; we resolve the Account ID at Contact import time so that each Contact's AccountId reference is satisfied. Deduplication checks run against existing Account records using company domain as the match key.

Crust CRM Deal records map to Freshsales Deal. Deal name, amount, close date, probability, and custom fields migrate directly. The Crust CRM pipeline and stage assignment maps to a Freshsales Deal Pipeline and Stage that we configure during the Freshsales setup phase. Pipeline stage names from Crust CRM are translated via the translation table generated during discovery. Owner assignment migrates by email match against Freshsales User records.

Crust CRM pipelines and stage names are organization-specific and cannot be imported directly into Freshsales. We collect the full pipeline-stage map during discovery, then configure corresponding Deal Pipelines and Stages in Freshsales during the setup phase before any Deal records are imported. Stage probability percentages translate to Freshsales stage probability values rounded to the nearest supported integer.

Crust CRM engagement records for calls, emails, meetings, and notes map to Freshsales Tasks and Events. Call duration and disposition migrate to custom Task fields; email content migrates to Task notes with sender and recipient preserved; meeting start and end times migrate to Event with location preserved; notes migrate as Freshsales Notes linked to the parent Contact or Account. We use Freshsales's REST API for activity insertion rather than CSV import because parent-record resolution requires sequential processing to satisfy the relationship references.

Crust CRM's configurable module architecture means organizations may have unique custom objects not present in a standard CRM install. We enumerate all custom objects during the pre-migration schema audit, map each field type to a typed Freshsales custom field, pre-create the custom object schema in Freshsales (including any lookup relationships to standard objects) before importing data, and flag any field types that have no Freshsales equivalent for customer review during scoping.

Crust CRM Owner records map to Freshsales User by email match. Any Owner without a matching Freshsales User is flagged in a reconciliation queue before record migration begins. The customer's admin provisions missing Users in Freshsales (active status if the original owner is current, inactive if the owner has left the organization) before migration resumes. OwnerId references on Deals and Contacts cannot be satisfied without resolved User records.

Crust CRM attachments stored per record are exported individually with filename and record association preserved. For self-hosted Crust CRM instances, file storage location depends on the storage backend configuration; we coordinate with the customer's technical team to access the file system or object storage during export. Files are re-attached in Freshsales via the Attachments API, maintaining the parent record linkage. File type and size limits per Freshsales documentation apply.

Crust CRM tags stored as label fields on any object migrate to Freshsales Tags, which is a native tag management feature available across Contacts, Accounts, Deals, and other standard objects. Tags used for content classification or lead scoring are preserved as-is; no transformation is required because both platforms support multi-value tag assignment.

Crust CRM's enterprise messaging and identity management modules are platform-specific features with no direct Freshsales equivalent. We export these as JSON metadata during the Crust CRM schema audit and deliver the output in the migration handoff documentation. The customer's admin reviews the export and rebuilds relevant configurations manually in Freshsales using Freshworks's admin settings. This object is listed for transparency: no structured data record migration occurs for these modules.