Migrate from Sercom to Freshsales

Sercom contacts map directly to Freshsales Contacts when the record has an associated company and shows commercial activity. Email, phone, job title, and address fields carry over directly. Records without company association land as Freshsales Contacts linked to a default account.

Sercom contacts that have never been converted to a job or deal route to Freshsales Leads rather than Contacts. This applies to imported lists, cold leads, and marketing contacts that never engaged with a service ticket. Freshsales Lead Status pick-list values are mapped to Sercom's original status labels.

Sercom companies map to Freshsales Accounts using name, domain, industry, employee count, and annual revenue fields directly. Parent-child company hierarchies in Sercom map to Freshsales Account.ParentId. Multi-company associations on a single contact collapse to a primary AccountId plus Account Contact Relationships.

Sercom jobs contain technician assignments, scheduling windows, service types, and status fields. Freshsales has no native work-order object, so jobs become Tasks with Subject, Due Date, Status, and Priority fields. Technician assignment maps to Freshsales Task Owner; service type becomes a custom Task field. Jobs with line items require a custom Job Products object.

Sercom recurring jobs with subscription-style service agreements map to a custom Jobs object if your Freshsales plan includes custom modules (Enterprise). If not, recurring jobs become a series of Tasks with a recurrence custom field preserved as text for reference.

Sercom assets track equipment linked to accounts with maintenance history, serial numbers, and install dates. Freshsales has no native asset object; assets migrate as a custom Asset object with fields for AccountId lookup, equipment name, serial number, install date, and last service date. Enterprise plan required for custom modules.

Sercom call logs, emails, and meeting records map to Freshsales Tasks (Type: Call or Email) and Events (meetings with start/end times). Original timestamps, activity owners, and parent-record links (contact, company, or job) are preserved in Freshsales. Rich-text body content migrates as Salesforce Notes.

Sercom notes attached to contacts, companies, or jobs migrate to Freshsales Notes linked to the corresponding record. If Sercom stores notes as HTML, we strip formatting to plain text unless Freshsales Rich Text fields are available in your plan. We recommend verifying note rendering in the target environment after migration.

File attachments on Sercom records are downloaded and re-uploaded to Freshsales Files, preserving original file names and, where available, the created-date metadata. File size limits follow Freshsales' 25MB per-file cap; oversized files are flagged for manual handling. We also verify that file types are supported in Freshsales before upload.

Sercom products or service items map to Freshsales Products with name, description, unit price, and currency. Products linked to jobs become line items in a custom Job Products object or as custom fields on the Task representing the job. We also ensure that product pricing is converted to the target currency using the latest exchange rates.

Sercom users and technicians resolve to Freshsales Users by email match. Unmatched users are flagged before migration — your team either creates the Freshsales user first or assigns records to a fallback owner. Role and permission structures do not migrate as those are destination-side configuration.

Any Sercom custom properties on contacts, companies, jobs, or assets require a corresponding custom field in Freshsales. We create the field in Freshsales Admin Settings under the appropriate module (Leads, Contacts, Accounts, Deals, Tasks) and map the values. Type mismatches (e.g., Sercom unstructured text to Freshsales picklist) require manual value-mapping setup.