Migrate from Tubular CRM to Pipedrive

Tubular Contact records map to Pipedrive Person records. We transfer names, email addresses, phone numbers, company association, owner assignment, and any custom Contact-level fields. The Tubular Contact-Company relationship maps to a Person-Organization link in Pipedrive. If the Tubular account is on Enterprise with API access, we pull Contacts via the API; on Pro tier we use the UI-based CSV export, which requires the customer to download from the Contacts section before Deals to preserve the relational sequence.

Tubular Lead records map to Pipedrive People with the 'is_lead' flag set to true, routing them to the Leads inbox. The Lead Builder fields from Tubular translate to Pipedrive custom fields on the Person object. Lead source, status, and owner assignment map to corresponding Pipedrive fields. Leads without an email address are flagged as incomplete for the customer to review post-import since Pipedrive requires an email address for People records in most integrations.

Tubular Companies map directly to Pipedrive Organizations. The company name, domain, industry, phone, address, website, and owner assignment transfer. Organization is created first during import so that the Person-Organization lookup is satisfied when People records are inserted. Deduping is performed on company domain and name to prevent duplicate Organizations in Pipedrive.

Tubular Deals map to Pipedrive Deals with deal name, value, currency, expected close date, owner, stage assignment, associated Person, associated Organization, and deal-level notes preserved. Tubular's payment terms and weighted forecast values transfer as custom fields in Pipedrive. Deal stage history is reconstructed from Tubular's stage timestamps where available in the export.

Each Tubular deal pipeline and its stages are translated into a Pipedrive Pipeline with corresponding Stages. Stage order and stage names map directly. Stage-specific metadata such as probability percentages (where configured in Tubular) transfer to Pipedrive Stage probability values. Multiple Tubular pipelines map to multiple Pipedrive Pipelines only if the customer is on Pipedrive Growth or above.

Tubular Tags on Deals and Contacts transfer as Pipedrive Labels, which appear as multi-select fields on Deal and Person records. We flatten Tag arrays from Tubular and create matching Label values in Pipedrive during schema setup. Tags that appear across both Contacts and Deals result in identical Label sets in both Pipedrive objects.

Tubular Tasks associated with Deals and Leads map to Pipedrive Activities with type=Task. We transfer task title, due date, completion status, owner, and any task notes. Recurring task patterns are not supported in Tubular's export and are flagged in the handoff document for manual rebuild in Pipedrive's automation builder.

Tubular email logs, call logs, and meeting records attached to Deals and Contacts migrate as Pipedrive Activities. Call dispositions and durations transfer as custom fields. Meeting location, start time, and end time preserve. Each activity is linked to the correct Person and Deal via Pipedrive's activity sub-resources. Where Tubular's API is unavailable (Pro tier), these records are extracted from CSV exports with activity type inferred from column headers.

Tubular's Lead Builder custom fields on Lead records (available on both Pro and Enterprise) map to Pipedrive custom fields on the Person object. We pre-create the destination custom fields during schema setup, matching field types (text, numeric, date, dropdown) and inheriting any picklist values as Pipedrive options. The customer chooses which Lead Builder fields to migrate during scoping.

Tubular User accounts and deal owners map to Pipedrive Users. We resolve by email match. Any Tubular Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's Pipedrive admin to provision before record import resumes. Inactive Tubular users are flagged for reassignment during scoping.