Migrate from SwiftCRM to Freshsales

SwiftCRM has no native Lead object — all client records are Contacts with a relationship type property. During scoping we evaluate whether each SwiftCRM Contact maps to a Freshsales Lead (unqualified prospect) or Contact (qualified or existing client). We use SwiftCRM relationship type and any sales-stage metadata to drive the split. The original SwiftCRM relationship type preserves as a custom field on the Freshsales record for audit. Email is the dedupe key for Freshsales import.

SwiftCRM Contacts with a business relationship type and company name map to Freshsales Account records. We extract the company name from SwiftCRM's relationship property and create the Account first, then link the Contact via the AccountId lookup during Contact import. This ensures the Contact-to-Account relationship is satisfied at insert time rather than requiring a follow-up update pass.

SwiftCRM Appointments with client links, start/end timestamps, reminders, and notifications map to Freshsales Event records. We preserve the client link via EventRelation records that point to the migrated Contact. If SwiftCRM stores location or meeting notes, those migrate to Event Location and Description fields. Appointment reminders from SwiftCRM that are time-based create corresponding Freshsales Task records with the same due date.

SwiftCRM Reminders tied to specific clients or appointments map to Freshsales Task records. Task Subject carries the SwiftCRM reminder description, and the linked Contact migrates via the Contact lookup. Status defaults to Open in Freshsales unless the SwiftCRM reminder is marked complete.

SwiftCRM client documents export as files and attach to the corresponding Contact or Account record in Freshsales. We extract the full file set, map filenames to their client record, and upload via Freshsales file API. Any folder hierarchy in SwiftCRM's e-doc organization documents as a note on the Contact so the admin can replicate the structure in Freshsales.

Notification history tied to client interactions migrates as Freshsales Note records linked to the Contact. We preserve the notification text, timestamp, and type as Note body content. This captures the SwiftCRM-native notification context without creating a custom field for every notification type.

SwiftCRM relationship structures (family, business, referral) between Contacts map to Freshsales custom Contact fields. We configure a multi-select picklist field on Contact during pre-migration schema setup with the relationship type values extracted from SwiftCRM. If SwiftCRM stores relationship direction (e.g., spouse of, referred by), we capture that as a second custom field.

SwiftCRM beta-stage custom fields vary by account tier. We audit available custom fields during scoping and map each to an equivalent Freshsales custom field with matching data type. We configure Freshsales custom fields via Admin > Custom Fields before any data import so that the import wizard recognizes the fields. Any custom fields with unavailable Freshsales data types migrate as text fields with the original type noted for admin review.

SwiftCRM user accounts map to Freshsales User records. We resolve by email match. Any SwiftCRM user without a matching Freshsales User goes to a reconciliation queue for the admin to provision before record import resumes. User permissions and roles document from SwiftCRM during scoping for the admin to configure in Freshsales post-migration.