Migrate from LionDesk to Pipedrive

LionDesk Contact maps directly to Pipedrive Person. Every standard field (name, email, phone, address) transfers as-is. LionDesk contacts without an associated company land as standalone Persons in Pipedrive — FlitStack links the primary company via org_id after Organization records are migrated.

LionDesk Company maps to Pipedrive Organization. Company name, domain, industry, employee count, and annual revenue transfer as direct field mappings. Parent-child company hierarchies in LionDesk map to Pipedrive's parent_org_id on the Organization record, resolved in dependency order. FlitStack processes Organizations before Persons to ensure org_id foreign keys are valid when Person records are loaded.

LionDesk Deal maps to Pipedrive Deal by object name. The LionDesk pipeline that a deal belongs to determines which Pipedrive Pipeline the deal lands in. Deal amount, close date, stage name, and owner_id transfer with value-mapping for stage pick-list values to ensure the deal lands in the correct Pipedrive stage.

Each LionDesk pipeline becomes one Pipedrive Pipeline. FlitStack reads the LionDesk pipeline configuration including stage names and stage order, then creates the equivalent Pipeline in Pipedrive before any Deal records are migrated. This ensures the foreign-key reference (pipeline_id and stage_id) on each Deal resolves correctly when the deal records are loaded into the target system.

LionDesk stage names map to Pipedrive Stage names within each Pipeline. Probability values assigned to each stage in Pipedrive are set according to your specified mapping rules. Stage-entered timestamps from LionDesk are preserved as custom datetime fields on the Pipedrive Deal for reporting continuity.

LionDesk call records migrate as Pipedrive Activities with type='call'. The call duration, outcome, owner, and original timestamp transfer as direct field values. Each Activity is linked to the corresponding Person or Deal via the activity_bits JSON structure in the source record, maintaining the relationship trail that agents rely on for deal history review.

LionDesk emails, meetings, and notes migrate as Pipedrive Activities with type='email', 'meeting', or 'note' respectively. Subject line, body content, timestamps, and owner assignments transfer completely. Pipedrive's unified Activity model consolidates what LionDesk stores as separate engagement types into a single activity stream per record, providing a cleaner timeline view in the UI.

LionDesk custom fields (Text, Number, Date, Dollar Amount) map to Pipedrive field types varchar, int/double, date, and monetary respectively. Pipedrive field keys are generated as 40-character hashes — FlitStack records the mapping between the LionDesk field ID and the Pipedrive key so data writes correctly. Custom fields on Deals also appear on Leads in Pipedrive automatically.

LionDesk drip campaigns and text/email sequences have no structural equivalent in Pipedrive. Pipedrive uses Sequences (email step automation) and Automations (condition-triggered workflows), which use a different trigger-and-action model. FlitStack exports campaign definitions as a JSON reference file that your Pipedrive admin can use to rebuild them in Sequences and Automations.

LionDesk's native SMS/texting capability has no direct Pipedrive equivalent — Pipedrive stores email and call history as Activities but does not natively surface SMS threads as records. If SMS content was stored as notes in LionDesk, those notes migrate as Pipedrive note Activities. Your team should configure a third-party SMS integration (such as a Zapier-connected texting tool) in Pipedrive post-migration.

LionDesk owner IDs resolve to Pipedrive User records by email address match. FlitStack flags any LionDesk owner without a corresponding Pipedrive user before migration begins. Those records are assigned to a fallback Pipedrive user or held in a 'To Assign' state until your team creates the missing Pipedrive user accounts.

LionDesk tags applied to contacts or deals map to Pipedrive custom enum fields if the tag vocabulary is small and consistent. For large or unstructured tag sets, FlitStack creates a text custom field and stores tags as a comma-separated string, preserving the data for post-migration review and cleanup.