Migrate from The Customer Factor to Pipedrive

TCF 'Customers' map directly to Pipedrive 'People'. The primary contact record — name, email, phone, address — maps field-by-field. Each TCF customer must be linked to a Pipedrive Organization (created from TCF company data or from the customer's company name field).

TCF 'Prospects' map to Pipedrive 'Leads' rather than People when the prospect has not yet been converted to a TCF customer. Pipedrive Leads have a separate field set from People, so FlitStack maps TCF prospect-specific fields (e.g., source, interest level) to custom fields on the Lead object.

TCF does not have a standalone company object — company name is stored as a property on the Customer or Prospect record. FlitStack extracts all unique company names, deduplicates them, and creates Pipedrive Organization records. Each Person is then linked to their primary Organization via organization_id.

TCF estimates (with line items, amounts, and status) are the closest analogue to Pipedrive deals. FlitStack maps estimate amount to deal value, estimate status (e.g., sent, approved) to a Pipedrive stage in a designated 'Estimates' pipeline, and the original TCF estimate ID to a custom field on the deal for traceability. If a TCF estimate converted to a job, the job's status maps to a separate pipeline stage in the same deal.

TCF jobs (scheduled service records with crew, date, and completion status) have no direct Pipedrive equivalent. Pipedrive's project management features (available on Power and Enterprise plans) can track tasks within a deal, but a full job record is stored as a custom field block on the deal linked to the original estimate. Job status, scheduled date, and completion notes are preserved as custom fields rather than native objects.

TCF status values — estimate sent, estimate approved, job scheduled, job in progress, job completed, invoice sent, invoice paid — are mapped value-by-value to Pipedrive deal stages. FlitStack creates a dedicated pipeline in Pipedrive (e.g., 'Field Service Pipeline') with stages that mirror the TCF status workflow, so the deal's stage history reflects the full service lifecycle from quote to payment.

TCF invoices (billing records with line items, tax, and payment status) cannot be stored as Pipedrive objects — Pipedrive has no native invoice entity. FlitStack preserves the invoice ID, amount, and payment status as custom fields on the related deal and exports invoice data as a supplementary CSV that teams can connect to their accounting tool (QuickBooks, Xero) post-migration.

TCF notes and call logs attached to customer, prospect, or job records migrate as Pipedrive Activities. Emails, calls, and meetings map to Pipedrive activity types (email, call, meeting). Each activity is associated with the correct Person and, where applicable, the related Deal. Original timestamps and owner (assigned to user by email match) are preserved.

TCF custom properties (e.g., service type, property address, crew lead, insurance carrier, job type) have no Pipedrive native equivalent. FlitStack creates Pipedrive custom fields via POST to the appropriate /Fields endpoint, captures the returned hash key, then populates those fields during the data write phase. Fields are created per object — a custom property on TCF Customers becomes a custom field on Pipedrive Person.

TCF does not have a formal user-object API. FlitStack resolves TCF owner assignments by matching the owner email embedded in exported records against Pipedrive user emails. Unmatched owners are flagged before migration; their records are assigned to a designated fallback Pipedrive user and logged for admin review.

TCF file attachments (e.g., job photos, signed estimate PDFs) attached to customer or job records are downloaded and re-uploaded to Pipedrive as Files linked to the corresponding Person or Deal. Pipedrive's file storage limits per plan apply — Essential includes 5GB/user, higher plans include more.