Migrate from m-savvy to Freshsales

M-savvy Contacts map directly to Freshsales Contacts with all standard fields (name, email, phone, address, lifecycle stage, owner assignment) preserved. The email address serves as the dedupe key during import. Custom contact fields discovered via m-savvy API inspection map to Freshsales custom fields of equivalent data type. Owner assignment resolves via email match against Freshsales User records before Contact insert.

M-savvy Account records representing organizations map to Freshsales Accounts. Industry, size classification, and billing address fields map directly. The account-contact relationship is preserved during migration by ensuring Account records are created before the Contact import phase. If a contact has no linked account in m-savvy, it migrates as a standalone Freshsales Contact without an AccountId.

M-savvy Deals tracking pipeline opportunities map to Freshsales Deals. Stage name, deal amount, close date, probability, and owner assignment migrate. Custom deal fields discovered in the m-savvy schema map to Freshsales custom fields on the Deal object. Any m-savvy deal-stage names that do not match Freshsales default stages are created as new stage values in Freshsales during the configuration phase.

M-savvy Leads are distinct from Contacts and map to Freshsales Leads with lead status, lead source, and owner preserved. Lead score values stored in custom m-savvy fields migrate to Freshsales custom fields. During migration scoping, if the customer's m-savvy workflow merges Leads into Contacts at conversion, we design the Lead-to-Contact conversion mapping in Freshsales to match the original behavior.

M-savvy pipeline definitions and custom stage names are read from the live API during discovery. We create matching Freshsales Deal pipelines with equivalent stage values before Deal import begins. If m-savvy has multiple pipelines, we create multiple Freshsales pipelines with the customer's pipeline-to-record mapping preserved. Stage probabilities migrate to Freshsales stage probability settings.

M-savvy Activities linked to Contacts or Deals migrate to Freshsales Task and Appointment records. Emails and calls map to Tasks; meetings map to Appointments. Activity type, timestamp, owner, and linked record associations (ContactId, DealId) are preserved. Archived or deleted activities are excluded. Any attachment associations on activities are flagged because m-savvy stores attachments separately from records.

M-savvy custom objects require live API inspection during discovery because m-savvy does not publish a public schema reference. We enumerate each custom object type and its fields, then pre-create matching Freshsales custom objects and fields before data import. Custom object records migrate last, after all parent standard objects are in place, because custom objects in Freshsales often contain lookup relationships to Contacts, Accounts, or Deals. We resolve those lookups at migration time using the imported record IDs.

M-savvy attachment files are stored separately from record data and require a dedicated export pass using m-savvy file API endpoints. We download files to our staging environment, then re-upload to Freshsales and relink each file to its parent record by ID. If a parent record fails to migrate, its attachments are held in a flagged queue for manual review. Large attachment libraries (over 50 GB) extend migration timeline because file transfers require sustained bandwidth and Freshsales upload limits per batch.