Migrate from Kickserv to Pipedrive

Kickserv Customer maps directly to Pipedrive Organization. Company name becomes Organization name, phone maps to phone, email maps to email, website maps to website, and address fields (street, city, state, zip) map to their Pipedrive address counterparts. Custom fields on the Kickserv Customer are created as Pipedrive Organization fields before import.

Kickserv Contact maps to Pipedrive Person. Name fields split into first_name and last_name, email maps to email, phone maps to phone, mobile maps to mobile. The Kickserv Customer link becomes the Pipedrive OrganizationId lookup — the Organization must exist before the Person import to resolve the foreign key correctly.

Kickserv Job maps to Pipedrive Deal — the core transformation in this migration. Pipedrive Deal has no native job_status, job_type, or technician field, so we create custom fields on the Deal to preserve ks_job_status, ks_job_type, ks_technician_name, and ks_scheduled_date. The original Kickserv job ID is stored as ks_source_id for delta-run de-duplication.

Kickserv Estimate amount maps to Pipedrive Deal amount. Each estimate line item (service, quantity, unit_price) maps to a Pipedrive Product linked to the deal via deal_product — this requires Products to be pre-created in Pipedrive with matching names before the migration runs.

Pipedrive has no native invoice object. Kickserv Invoice is preserved as a custom text field on the Deal (ks_invoice_url) storing the Kickserv invoice URL and payment status. If the team uses QuickBooks Online for invoicing, the Kickserv-QuickBooks link is not migratable — invoices must be recreated in the destination accounting tool.

Kickserv Employee maps by email match to an existing Pipedrive User — the deal owner resolves to that UserId. Unmatched employees are stored as a custom field (ks_technician_name) on the deal. Kickserv employee roles and permissions have no Pipedrive equivalent and must be reconfigured in Pipedrive user management post-migration.

Pipedrive has no native time-tracking object. Each Kickserv Time Entry (employee, date, hours, notes) is stored as a set of custom fields on the associated Deal — ks_time_employee, ks_time_date, ks_time_hours, ks_time_notes — concatenated for records with multiple entries per job.

Kickserv Service maps to Pipedrive Product. Service name becomes Product name, price maps to unit_price, and unit maps to product_variable flag. Pre-creating Products in Pipedrive is required before Deal import so line items can link via deal_product correctly. If the Service uses variable pricing, set product_variable to true. FlitStack validates that each Service exists in Pipedrive before Deal import to avoid linking errors.

Kickserv Item maps to Pipedrive Product. Item name becomes Product name, item_cost maps to cost, and quantity_on_hand maps to stock_quantity. Items used in estimates need Products pre-created in Pipedrive with the same name for correct deal_product linking. If an Item has a zero cost, the Product will have a cost of zero; you can adjust later in Pipedrive. FlitStack validates that all Items are present in Pipedrive before Deal processing.

Pipedrive deals do not support tags natively — tags exist for Activities and People only. Kickserv Tags are concatenated into a single ks_tags custom field on the Deal as a comma-separated text value, preserving the tagging context for manual review in Pipedrive.

Kickserv Note maps to Pipedrive Note with activity_type=note. The note body maps to content, the linked customer or job maps to the Person or Deal association in Pipedrive. Original timestamps are preserved. Kickserv note character limits align with Pipedrive's long-text field capacity.

Kickserv Signatures attached to Jobs or Invoices are downloaded and re-uploaded as Pipedrive Files attached to the corresponding Deal. Pipedrive Files support PDF and image formats up to 100MB. The original filename and timestamp are preserved in the file metadata.