Migrate from Teleforce CRM to Freshsales

Teleforce Contact records map to Freshsales Contact. We extract via CSV using standard field names (first_name, last_name, email, phone, address fields) and map to Freshsales Contact object fields. The Freshsales contact_id is generated on import. Custom fields on Teleforce Contacts require manual field name extraction from the CSV header row and mapping to pre-created Freshsales custom fields. Owner assignment maps via email match to Freshsales User records.

Teleforce Company records map to Freshsales Account. The company_name field maps to account_name, and any industry, website, phone, or address fields map to their Freshsales equivalents. We extract Accounts first in the migration sequence so that AccountId is available as a lookup on Contacts before Contact import begins. If Teleforce Company records have a linked contact count, we validate that all linked Contacts resolve to an existing AccountId.

Teleforce Deal records map to Freshsales Deal. Deal name, amount, stage, expected_close_date, and owner_id transfer directly. Pipeline stage names in Teleforce must be confirmed from the UI during discovery and mapped to Freshsales pipeline stage values we create before migration. If Teleforce deal records include a linked company_id or contact_id, we resolve those to Freshsales AccountId and ContactId respectively.

Teleforce pipeline configuration (stage names, stage order, stage probabilities) must be extracted from the UI during discovery since no programmatic export is confirmed. We recreate the pipeline structure in Freshsales before Deal import: creating the pipeline, adding each stage with matching names, and setting stage probabilities. Stage status options (open, won, lost) map from Teleforce deal status to Freshsales deal_status field.

Teleforce call records from the unified inbox export to CSV where available. We map to Freshsales Task records with type set to Call. Call duration, disposition, and timestamp transfer to custom task fields. The Task is linked to the parent Contact or Account via WhoId and WhatId. If Teleforce call records do not export cleanly, we flag this as a partial activity gap in the discovery report.

Teleforce email records from the unified inbox map to Freshsales Activity records with type Email. Subject, body (plaintext), timestamp, and sender/recipient addresses transfer. We link each Activity to the parent Contact or Account. Email attachments cannot be confirmed as exportable from Teleforce; we document the attachment gap in the migration report and leave inline attachments in the source system as a manual follow-up item.

Teleforce task records (follow-ups, reminders, to-dos) map to Freshsales Task. Task subject, due_date, status, priority, and owner transfer. We resolve the owner by email match against Freshsales User records. Completed status maps directly. Tasks without a matching owner go to a reconciliation queue.

Teleforce custom fields on Contacts and Deals require manual extraction: we request a full CSV export and inspect the header row for non-standard field names. Each identified custom field is pre-created in Freshsales with the matching field type (text, number, date, picklist, checkbox) before migration begins. Field dependencies configured in Teleforce are documented in the migration inventory and rebuilt manually in Freshsales using Freshsales field dependency rules.

Teleforce user records and owner assignments on Contacts, Companies, and Deals are resolved by email address against Freshsales User records. We extract the distinct owner_email values from all record types and create a mapping table before migration. Any Teleforce owner without a matching Freshsales User goes to a manual provisioning queue; migration of records assigned to unprovisioned owners is deferred until the customer provisions the User.

Teleforce Lead records (if present as a distinct lifecycle stage or record type) map to Freshsales Lead. We handle lead-to-contact conversion mapping on a per-customer basis because Teleforce lead lifecycle logic varies by account configuration. The conversion decision (whether a Teleforce lead becomes a Freshsales Lead or Contact) is confirmed during discovery based on the customer's current Teleforce setup.