Migrate from Teleforce CRM to Pipedrive

Teleforce Contacts map to Pipedrive Persons. We extract contacts via CSV from Teleforce's UI or via negotiated database access, then import using Pipedrive's Person endpoint or Import2 tool. All standard fields (name, email, phone, address) map directly. Custom fields on Teleforce contacts are extracted as additional columns and mapped during the import step to Pipedrive custom fields, which are created beforehand in the destination. Owner assignment resolves by email match against Pipedrive User records.

Teleforce Companies map to Pipedrive Organizations. Organization records are imported before Person records so that the organization_id foreign key is available at Person insert time. We use company name as the dedupe key during import to prevent duplicate organizations. Teleforce's company-contact associations are preserved by linking each Person to its parent Organization after both objects are loaded.

Teleforce Deals map to Pipedrive Deals using a 1:1 field mapping. Deal name, value, stage, expected close date, and owner migrate directly. The Teleforce dealstage name maps to the nearest Pipedrive stage label, with stage probability percentages rounded to Pipedrive's allowed integer range. We pre-create the Pipedrive pipeline and stages before the Deal import phase begins so that stage IDs are available for assignment.

Teleforce Pipelines are recreated as Pipedrive Pipelines. During discovery we request a screenshot or field list of Teleforce's current pipeline names and stage order. Each pipeline is created in Pipedrive with matching stage labels and explicit probability values per stage. Pipeline assignment on Deals resolves during the Deal import phase by matching Teleforce pipeline name to the pre-created Pipedrive pipeline.

Teleforce Activities (call records, email references, SMS logs, chat threads) are decomposed into Pipedrive Activity records. Call logs map to Pipedrive Notes with a phone_call type flag. Email references map to Notes with email type. We flag the limitation that raw email body content and chat transcript threads require Teleforce's unified inbox export confirmation; without a confirmed export path, activity migration is limited to structured field data rather than full conversation history. This is explicitly called out in the gotchas section.

Teleforce custom fields on Contacts are mapped to Pipedrive custom Person fields. During discovery we request a full list of active custom field names and their data types (text, number, date, dropdown). Pipedrive custom fields are pre-created in the destination with matching field types before the Person import begins. Multi-select or tag-based Teleforce fields map to Pipedrive multi-select picklists. This work depends on Teleforce exposing the full custom field inventory during discovery.

Teleforce custom fields on Deals map to Pipedrive deal custom fields. We follow the same pre-creation pattern as custom Person fields: names and types are confirmed during discovery, Pipedrive fields are created in the sandbox before production migration, and values are included as columns in the Deal CSV or API payload. Custom fields that reference lookups to other Teleforce objects require manual remapping if the destination lookup does not exist in Pipedrive's schema.

Teleforce Leads are imported as Pipedrive Leads if the customer enables the Leads feature in their Pipedrive account settings (available from the Growth plan and above). Lead status and source fields map to Pipedrive Lead fields. If the customer prefers a Contact-first model without a separate Lead object, we import Leads as Persons with a lifecycle_stage custom field to preserve the original record type. The choice is confirmed during scoping before migration begins.

Teleforce User records and owner assignments on Contacts, Companies, and Deals are resolved by email match against Pipedrive User records. We extract every distinct owner email from the source data and compare against the provisioned Pipedrive user list. Owners without a matching Pipedrive User are placed in a reconciliation queue; the customer provisions the missing users before the production import phase runs. Orphaned owner references (owner_id in Teleforce with no email match) are logged separately.

Teleforce tag support was not confirmed in the available research, and the platform's FlitStack AI source page marks Tags/Labels as support:none. Where tags are identified during discovery as active metadata on records, we treat them as custom text fields and migrate them to Pipedrive as a multi-select custom field or as comma-separated values in a text field. The specific approach is confirmed per-customer based on what Teleforce actually exposes in its export.

Teleforce stores attachments within the CRM context but we found no documented path to export attachments in bulk. We extract attachment file names and URLs where they appear in the source CSV as text fields, and attach them as Note records in Pipedrive with the original filename in the title. Actual file blob migration is out of scope unless the customer provides direct database access that exposes the attachment storage layer.