Migrate from Sage CRM to Freshsales

Sage CRM Companies map directly to Freshsales Accounts. The CompanyName field becomes Account Name, and address fields map to Freshsales address fields. We extract all standard Company fields plus any custom Company fields from Sage CRM and create corresponding custom fields on the Freshsales Account object during schema setup. The CompanyID becomes the dedupe key during import to prevent duplicate Account creation.

Sage CRM Contacts link to Companies via PrimaryCompanyLink. We extract all standard Contact fields plus custom Contact fields, preserve the company association by resolving PrimaryCompanyLink to the Freshsales Account record created in the previous phase, and import Contacts with Account_id populated. Duplicate detection uses email address as the unique identifier in Freshsales.

Sage CRM Lead records have their own lifecycle stages, qualification fields, and source tracking that map directly to Freshsales Lead fields. Lead status values from Sage CRM map to Freshsales Lead Status using a status translation table created during scoping. If the customer uses Sage CRM lead scoring, we preserve that value in a custom Lead field for reference in Freshsales.

Sage CRM Opportunities track pipeline stages, revenue amounts, expected close dates, and owner assignments. These map to Freshsales Deals with stage names translated via a stage mapping table, amount mapping to Deal Amount, and expected close date mapping to Close Date. Owner assignment resolves via email match to Freshsales User records. Multi-currency amounts from Sage CRM map to Freshsales Deal currency and amount fields.

Sage CRM Cases have severity, status, and assignment fields that map to Freshsales Case object fields. Case-threaded communications stored in the Sage CRM Communication table linked by case ID migrate as conversation entries on the Freshsales Case. If the customer used a custom Case status workflow in Sage CRM, we create corresponding Case status values in Freshsales during schema setup.

Sage CRM Communication table stores email history linked to entity IDs (Company, Contact, Lead, Opportunity, or Case). We filter Communications by communicationtype = email and migrate each as a Freshsales Task with type = Email, the original email body as the Task description, and the associated Sage CRM entity resolved to the corresponding Freshsales record ID at migration time. The original timestamp preserves activity ordering.

Sage CRM call log entries in the Communication table with communicationtype = call migrate as Freshsales Tasks with type = Call. Call duration, disposition notes, and outcome from Sage CRM map to Freshsales Task custom fields. The associated Contact, Lead, or Opportunity reference resolves to the Freshsales record ID at migration time.

Sage CRM meeting records in the Communication table with communicationtype = meeting migrate as Freshsales Events with start_time, end_time, and location preserved. Attendee information from Sage CRM creates Event Relationship records pointing to the associated Freshsales Contacts or Leads. The original meeting notes migrate as the Event description.

Sage CRM Custom Entities have both display names and internal table names (e.g., CustomEntityname). We inspect the entity schema via the Sage CRM API model service to identify all custom fields and relationships, pre-create equivalent Custom Objects in Freshsales with matching field types, and import Custom Entity records with lookup relationships resolved to the parent Account, Contact, or Deal. Custom Entities with no clear Freshsales equivalent map to Notes or related-item structures on the parent record.

Sage CRM Users have role-based security profiles controlling object and field access. We extract all active and inactive User records with their role assignments. User provisioning in Freshsales requires the customer's Freshsales admin to create User accounts manually; we match existing Freshsales Users to Sage CRM Users by email and flag any Sage CRM User without a Freshsales match for manual provisioning before the main record migration begins.