Migrate from Swivl Tech to Pipedrive

Swivl Tech Customer records — containing name, email, phone, and contact history — map 1:1 to Pipedrive People. The primary email address maps to Person.email. Multiple customer contacts per location collapse to one Person record with additional contact details stored as custom fields or activity notes.

Swivl Customer company name and address data merges into a Pipedrive Organization record. When a Swivl Customer has a company name, FlitStack creates the Organization first, then links the Person record via Org ID. When no company name exists, the Person stands alone but is flagged for manual Organization creation in Pipedrive.

Swivl Location records — site name, full street address, city, state, ZIP, latitude/longitude — map to Pipedrive Organization address fields (address, city, state, zip, country) and custom GPS fields. Multiple Locations under one Customer become multiple Organization address entries linked to the same Person.

Swivl Job Order is the primary migration unit — every job becomes a Pipedrive Deal. The Deal title carries the job description, the associated Person becomes the Deal's linked contact, and the associated Organization becomes the Deal's organization link. Job status maps to a custom Deal field; job priority maps to a custom Deal field; work order number maps to a custom Deal field.

Swivl pipeline stages are mapped value-by-value to a Pipedrive custom pick-list field called Work_Order_Status__c. Each Swivl stage name is preserved as a Pipedrive pick-list value. The Pipedrive native Deal Stage field is configured separately for the sales pipeline, keeping operational job status distinct from sales pipeline stage.

Swivl Job Priority values (Low, Medium, High, Emergency) migrate to a Pipedrive custom pick-list field Job_Priority__c on the Deal. Values are mapped one-to-one preserving the source labels. If Swivl uses numeric priority scores (1–5), FlitStack converts them to descriptive labels or retains the numeric value in a custom number field.

Swivl Technicians resolve to Pipedrive Users by email address match. If a Swivl technician has no email (common for field-only accounts), FlitStack creates a Pipedrive User with the technician's name and a placeholder email, flagging the record for admin verification before the migration finalizes. Multiple technicians assigned to one job create multiple Deal Activity assignments in Pipedrive.

Swivl job notes, site visit logs, and technician check-in records map to Pipedrive Activities — Tasks for notes and follow-ups, Events for scheduled site visits. Original timestamps and activity owners are preserved. Swivl GPS check-in coordinates are stored as a custom field on the Activity or as a note attachment.

Swivl custom properties per Customer, Location, and Job Order are enumerated by FlitStack before migration. Each custom property gets a corresponding Pipedrive custom field of the matching type (text, number, pick-list, date, or checkbox). Custom field keys in Pipedrive are generated as 40-character hashes via the API — FlitStack maps the source field label to the destination field key at migration time.

Swivl file attachments associated with job orders — photos, work order PDFs, signed forms — are downloaded and re-uploaded as Pipedrive Files linked to the corresponding Deal. Pipedrive's file storage limits apply per plan (5GB/user on Essential, 10GB on Advanced, 100GB on Professional). Large photo batches may require bulk re-upload via API.

Swivl invoices and billing records do not have a native Pipedrive equivalent — Pipedrive has no accounting module. FlitStack migrates invoice numbers, amounts, and statuses as custom fields on the Deal (Invoice_Number__c, Invoice_Amount__c, Invoice_Status__c). If your team requires full invoice history, a separate export from Swivl is recommended for accounting software integration.

Swivl scheduled job appointments map to Pipedrive Events with start time, end time, and linked Deal. Recurring job schedules (e.g., monthly maintenance visits) require Pipedrive Automation rules or a Calendly integration post-migration to recreate the recurring trigger logic. FlitStack provides a mapping template for recurring event creation to help administrators set up the automation triggers efficiently.