Migrate from Loyalistic to Pipedrive

Loyalistic Contacts map directly to Pipedrive Person records. Standard fields (name, email, phone, company name) map 1:1. Any Loyalistic custom fields on Contact are sampled during discovery and mapped to Pipedrive custom fields on Person, respecting Pipedrive's type system (text, number, date, enum). Email address is used as the dedupe key during import. Company name from Loyalistic maps to the Organization field on Person, triggering an Organization lookup or creation in Pipedrive.

Loyalistic Customer Profiles aggregate contact details with enrichment data from third-party sources. We migrate the underlying contact fields directly. Any enrichment provenance fields (source attribution, enrichment timestamp, confidence score) are stored as custom fields on the Person record in Pipedrive. Note that enrichment data from third-party sources may carry forward as static values; ongoing enrichment would require a Pipedrive enrichment integration post-migration.

Loyalistic Segments define group membership based on behavioural or demographic rules. The segment logic itself (the rule builder) cannot migrate. We export segment names and the full member contact list. In Pipedrive, we create Labels matching the segment names and apply them to the Person records. If Loyalistic segments overlap (a contact belongs to multiple segments), the same contact receives multiple Labels in Pipedrive. The customer reviews segment naming and label structure during scoping before the label set is created in Pipedrive.

Loyalistic Survey response records attach to the originating Contact. Survey question text and answer values are mapped to custom fields on the Person record in Pipedrive (question becomes field label, answer becomes field value). For surveys with free-text responses or branching logic that does not fit a flat custom field structure, we attach the response as a Note linked to the Person. The survey definition (question text, branching rules) is preserved in a written survey inventory document for the customer's admin to reconstruct in Pipedrive Forms or a third-party survey tool if needed.

Loyalistic Campaigns store the campaign title, status, and timing, with engagement events (opens, clicks, conversions, sends) stored as separate activity records. We map campaign metadata to a Deal record in Pipedrive (campaign title becomes Deal title, campaign start/end dates become custom Deal fields), and convert engagement events to Pipedrive Activities (open events become email-type activities, click events become note-type activities with the URL as body text, conversion events become a custom activity type or Deal update). This split requires explicit customer sign-off because it is a structural decision rather than a 1:1 mapping.

Loyalistic stores individual engagement events (a contact opened an email, clicked a link, converted on a landing page) as separate records. We batch these events per contact and convert them to Pipedrive Activity records with activity type (email, call, meeting, task, or a custom type for campaign events) and timestamps preserved. High-frequency engagement data (multiple opens per contact per day) is aggregated to avoid creating hundreds of individual activity records that would clutter the Pipedrive timeline; the customer specifies the aggregation threshold during scoping.

Loyalistic Tags are flat labels applied to contacts for grouping. These map directly to Pipedrive Labels with a 1:1 name mapping. Label application is performed after Person records are created so that all Person IDs are resolved before the tag import batch runs.

Loyalistic supports custom fields on the Contact object. We perform field-level sampling during scoping to identify all active custom properties, their data types (text, number, date, enum), and their population rates. Custom fields are created in Pipedrive as Person custom fields before the contact import batch runs. Pipedrive's field type system (text, varchar, numeric, date, enum) must match the Loyalistic source type; mismatches are resolved as part of the load map design.

Loyalistic Reports define saved views and metric filters. Report configurations (the query logic and filter criteria) do not have a Pipedrive equivalent. We export the report output as CSV during discovery — the rendered data, not the report definition — and import the CSV as static records or as a custom object in Pipedrive if the customer's Pipedrive plan supports custom objects. The report metadata and a description of what each report measures is documented in the migration handoff notes for the customer's admin to rebuild using Pipedrive's reporting and dashboard tools.

Loyalistic Email and workflow templates exist as reusable content assets. Template content and variable placeholders are exported during discovery. Pipedrive supports email templates with merge fields in its native template manager. We export the Loyalistic template HTML and variable names in a written template inventory; the customer's admin recreates these in Pipedrive's template editor because Pipedrive's merge field syntax differs from Loyalistic's variable model.