Migrate from SuiteCRM to Freshsales

SuiteCRM Accounts map directly to Freshsales Accounts. The SuiteCRM account name, industry, website, billing address, and phone fields map to Freshsales Account equivalents. We use Account Name as the dedupe key during import to prevent duplicate records. Account must be imported before any Contact import to satisfy the AccountId lookup on Contact records.

SuiteCRM Contacts map to Freshsales Contacts with direct field mapping on name, email, phone, title, and the primary Account link. Custom fields added via SuiteCRM Studio are identified by scanning the database for extended table columns (accounts_cstm, contacts_cstm) and recreated as Freshsales custom fields before import. We map the SuiteCRM modified_date and date_entered timestamps to Freshsales created_at and updated_at for historical accuracy.

SuiteCRM Leads map directly to Freshsales Leads with status, source, and assignment fields preserved. Note that Freshsales has a Lead Conversion feature that creates a Contact, Account, and Deal from a single Lead — we configure Lead conversion field mapping during the Freshsales setup phase so that custom fields on SuiteCRM Leads map correctly through the conversion process.

SuiteCRM Opportunities map to Freshsales Deals. The SuiteCRM sales_stage maps to Freshsales deal stage, amount maps to deal value, and closed_date maps to expected close date. We configure Freshsales Deal pipelines and stage values before migration to ensure that stage names and probability percentages are available for import. Multiple SuiteCRM pipelines require Freshsales Pro plan or above; we flag this at scoping if applicable.

SuiteCRM Cases (tracked in the Bugs module) map to Freshsales Cases. Case status, priority, description, and related Account or Contact link migrate directly. Freshsales includes a Service module on its Suite plan ($49/user); if the customer has Cases, we recommend enabling the Freshsales Service module during migration scope to avoid Cases living in the Sales CRM. Case conversations migrate as notes if the Service module is not activated.

SuiteCRM Products map to Freshsales Products with pricing information, descriptions, and taxonomy preserved. Products must be imported before Quotes to maintain referential integrity for line items. The SuiteCRM product catalogue size is assessed during discovery and Products are imported in the correct dependency order before Deals that reference them.

SuiteCRM Quotes map to Freshsales Quotes with line items linked to the Products catalogue. Quote body content, total amounts, and related Opportunity linkage transfer as data records. Quote PDFs are not migrated as binary files; we export quote data and recommend regenerating PDFs in Freshsales post-migration. Freshsales quoting is available from Pro plan ($39/user) and above.

SuiteCRM Contracts map to Freshsales Contracts with start date, end date, renewal status, and linked Account preserved. Renewal date fields transfer as Freshsales date types. Contract status values are mapped to Freshsales contract status options during field mapping configuration.

SuiteCRM Invoice records migrate to Freshsales Invoices. Both platforms track invoice payment status but neither has a native accounting ledger — we flag Invoice records as partial financial data and direct customers to their accounting system for AR/AP reconciliation. Invoice line items map to Freshsales Invoice Items referencing the Product catalogue.

SuiteCRM Campaigns map to Freshsales Campaigns with campaign type, status, start date, and budget preserved. Campaign target lists from SuiteCRM are mapped to Freshsales Lists. Note that Freshsales campaign features are basic — advanced email campaign automation may require Freshdesk or a separate marketing platform. We document the campaign structure in the migration handoff for the customer to decide on marketing replacement strategy.

SuiteCRM Document records store files on the server filesystem (typically /upload/) with database metadata records. We extract the file blobs alongside the metadata records, preserve file checksums for integrity validation, and upload files as Freshsales record attachments. File permission issues during extraction are a known SuiteCRM migration risk — we validate checksums after extraction and flag any files that fail integrity checks. The Documents module does not have a direct Freshsales equivalent; files attach to the parent Account, Contact, or Deal record.

SuiteCRM Users map to Freshsales Users by email address match. Active and inactive status is preserved. We export the full SuiteCRM Users table including usernames and email addresses during discovery. Users without a matching Freshsales User email go to a reconciliation queue for the customer admin to provision before record import begins, since OwnerId references on all records must be resolved before migration.