Migrate from LeadMaster to Freshsales

LeadMaster Accounts map directly to Freshsales Accounts (Freshsales uses the term Account for company/organization records). We preserve the primary contact link, all standard address fields, and custom properties as Freshsales Account custom fields. The Account is the first object we import because Deals and Contacts reference it via lookup.

LeadMaster Leads map to Freshsales Leads with all standard and custom fields preserved. We map the LeadMaster status, source, and lifecycle fields to Freshsales Lead Status and the corresponding custom fields. Smart Queue filter logic is documented during discovery; the customer rebuilds each saved filter as a Freshsales Segment. Lead conversion field mapping (Lead custom field to Contact/Account/Deal custom field) must be pre-configured in Freshsales Admin Settings before migration begins, per Freshsales best practices.

LeadMaster records that have already been converted (with a linked Account and Contact equivalent) are migrated as Freshsales Contacts with the AccountId lookup resolved. We map the original Lead status history to a custom field on the Contact for audit purposes. Any LeadMaster Lead with an existing Account association is processed after Accounts are loaded so the AccountId reference is satisfied.

LeadMaster Opportunities map to Freshsales Deals. Stage, amount, close date, owner, and pipeline assignment migrate. Custom pipeline stages from LeadMaster are mapped against Freshsales' default Deal stages during scoping, and any non-matching stages are added to the destination pipeline before import. Deal owner assignment resolves via email match against the Freshsales User table.

LeadMaster Cases migrate to Freshsales Cases with case number, status, priority, description, and associated Account/Contact preserved. Conversation threads migrate as Case Emails (EmailMessage records linked to the Case). Case Record Type and Status values are pre-configured in Freshsales before migration.

LeadMaster custom form field definitions and their submitted response data are extracted separately. Form field definitions are documented as a schema inventory. Form response data that maps to standard CRM fields migrates directly; non-standard fields that have no Freshsales equivalent are stored as custom properties on the relevant Account, Contact, or Deal object. Form layouts must be replicated in Freshsales form builder post-migration.

LeadMaster marketing Campaigns migrate as Freshsales Campaigns with campaign name, type, status, start date, and budget fields. Contact associations within the campaign migrate as Campaign Members. Email template content is exported and documented; automation sequences within the campaign are not migrated and are inventoried for rebuild in Freshsales Workflow.

LeadMaster Users and Owners map to Freshsales Users by email match. We export the full user list with role assignments and map them to Freshsales user profiles. The User CSV is the first migration artifact validated against Freshsales because every record import requires an OwnerId reference. Active/inactive status is preserved; any LeadMaster user without a matching Freshsales user is held in a reconciliation queue for admin provisioning before record import resumes.

LeadMaster logged activities (notes, call records, email history, calendar events) migrate to Freshsales Task (with TaskSubtype = Call for call records), Event, and Note objects. Activity timestamps, descriptions, and owner assignments are preserved. Freshsales' native bulk import supports up to 25,000 records per import; for larger activity volumes we chunk and batch the load. Activity attachments migrate as Notes linked via ContentDocumentLink to the parent record.

LeadMaster Smart Queue definitions and saved searches are documented during discovery as a filter inventory. Each Smart Queue is mapped to a Freshsales Segment or List View that the customer rebuilds post-migration. We provide a filter-by-filter translation table mapping LeadMaster field names and operators to Freshsales segment conditions.