Migrate from TeamSystem CRM to Pipedrive

TeamSystem Contact records (name, email, phone, address, owner assignment) map to Pipedrive Person. We extract contact fields in schema order and preserve owner-email references for mapping to Pipedrive Users. Standard fields map directly; custom contact properties require field-to-field mapping to Pipedrive's custom fields during the import step.

TeamSystem Company records map to Pipedrive Organization. The domain and address fields migrate to Pipedrive's Organization name and location fields. Where TeamSystem contacts are linked to a Company record, we set the Person-Organization association in Pipedrive during import using the company_id foreign key resolved at migration time.

TeamSystem Lead records with status, source, and scoring fields map to Pipedrive Lead. Lead lifecycle stages vary per TeamSystem configuration; we map the source stage value to Pipedrive's Lead Status picklist. If the destination Pipedrive account does not use the Lead object (many SMB teams work only with Person and Organization), we map Lead_Status as a custom property on the Person record instead.

TeamSystem Opportunity records (value, stage, expected close date, pipeline association) map to Pipedrive Deal. We preserve the pipeline stage ordering and deal amounts through explicit field-to-field mapping. The expected_close_date maps to Pipedrive's close_date, and deal_value maps to the weighted value field with probability applied from the source stage probability percentage.

TeamSystem pipeline configurations including stage names, probabilities, and sequence become Pipedrive Pipelines with matching stages. Custom pipeline configurations require field-level mapping since stage names and count vary per organization. We configure Pipedrive pipelines before any Deal import so that stage assignment is valid at insert time.

TeamSystem activity logs linked to Contacts or Deals map to Pipedrive Activity records. Activity types (call, email, meeting, task) map to Pipedrive Activity types, and custom activity fields require value mapping since the taxonomy differs between platforms. We link activities to the migrated Person and Organization records using external ID lookups to preserve the activity timeline against the correct contact.

Organization-specific fields on any standard TeamSystem CRM object are extracted from the field registry during discovery and mapped to Pipedrive custom fields of equivalent type (text, number, date, dropdown, multi-checkbox). Pipedrive custom fields are created in the destination account before import so that the mapping step has valid targets. Multi-checkbox fields from TeamSystem map to multi-select picklists in Pipedrive.

TeamSystem User accounts with role assignments and record ownership map to Pipedrive Users. User IDs in TeamSystem do not map directly to Pipedrive usernames, so we build a user mapping table during scoping using email as the reconciliation key. Pipedrive Users must exist before any Deal or Activity import so that owner assignment is valid. We flag any TeamSystem owner without a matching Pipedrive User for the customer to provision before the migration run continues.

Files linked to Deals, Contacts, or Activities in TeamSystem are exported by reference URL or direct download and re-attached in Pipedrive to the equivalent Deal or Person record. Attachment storage limits and expiry rules must be checked per TeamSystem organization before migration because some configurations prune attachments older than a defined retention period.

TeamSystem automated workflow configurations are stored in the ERP-CRM integration layer and are not exportable as discrete data. We document active workflow triggers, conditions, and actions during discovery and deliver a written inventory with recommended Pipedrive Automation equivalents. The customer's admin rebuilds these in Pipedrive's automation builder post-migration.