Migrate from Resulticks to Pipedrive

Resulticks Contacts migrate 1:1 to Pipedrive Persons. Standard fields (name, email, phone, address) map directly. We preserve the Resulticks contact ID in a custom field resulticks_id__c for audit trail and cross-reference. Organization assignment requires resolving the Resulticks company association to an existing or newly created Pipedrive Organization during migration. Owner assignment maps via email lookup to a Pipedrive User.

Resulticks Contact records contain company association data that we extract and consolidate into Pipedrive Organizations. The organization name, domain, industry, phone, and address fields map directly. Organizations are created before Person import to satisfy the OrganizationId lookup on Person records. Duplicate organization names are deduplicated during transform using domain-based matching.

Resulticks audience memberships are multi-value per Contact. We split each audience membership into individual Pipedrive Tags on the Person record. A Contact belonging to three Resulticks audiences receives three Pipedrive tags. We preserve the audience definition logic (filter conditions, event rules) in a written segmentation inventory so the customer's admin can rebuild equivalent saved views in Pipedrive using tag-based filtering. Audience size and membership counts are preserved in the inventory document.

Resulticks Campaigns represent the top-level marketing execution unit. We migrate campaign metadata (name, status, channel, scheduling) as Pipedrive Deal records with custom fields holding the original Resulticks campaign ID, channel type, and start date. The Deal pipeline and stage in Pipedrive require configuration before migration: we recommend a single pipeline named after the Resulticks campaign set or a 'Marketing Pipeline' if the customer prefers to keep marketing-initiated deals separate from sales pipeline.

Resulticks custom contact properties (legacy field types, multi-select values, computed date fields) vary by account configuration. We inspect the Resulticks field schema during scoping, map each custom property to a Pipedrive custom field of compatible type (text, number, date, single-select, multi-select), and pre-create the destination fields via Pipedrive API before migration. Multi-select properties from Resulticks map to Pipedrive multi-select picklists. Computed fields are migrated as their computed value, not the formula.

Resulticks Contact-level Tags migrate as Pipedrive Person tags. Tag counts and distribution are preserved at the Contact record level. Pipedrive's tag limit and display behavior are documented during scoping to ensure no tag overflow on high-volume contacts.

Resulticks behavioral events (page views, email opens, purchase events, custom track events) are extensive in volume and variable in schema. We migrate a configurable event window (typically the most recent 12 months) as Pipedrive Activity records attached to the Person. Event type maps to ActivitySubject, event timestamp to ActivityDate, and event metadata to a custom activity_fields__c JSON field. We do not attempt to normalize event schema into Pipedrive's native activity model because the data structures are incompatible. Event migration scope is agreed upon during scoping based on customer reporting needs.

Resulticks Journey flows store branching logic, wait conditions, AI-driven Genie decision nodes, and multi-channel step sequences in a proprietary format with no documented export mechanism. We photograph and document the full Journey map during discovery as a reference architecture for the customer's admin to rebuild in Pipedrive Workflow Automation. The Journey node content (copy, images, offer codes) must be exported separately from Resulticks and re-authored in Pipedrive. We do not migrate Journey flows as code or configuration.

Resulticks platform users map directly to Pipedrive Users via email match. Owner assignment on migrated Contacts and Deals resolves to the matching Pipedrive User. Resulticks user roles (Admin, Marketer, Analyst) do not have direct Pipedrive equivalents; we map to Pipedrive's Admin and Regular User roles during provisioning. Users without a matching Pipedrive User go to a reconciliation queue for manual provisioning.

Campaign body templates, images, and content assets from Resulticks cannot be automatically linked to Pipedrive Deal records. We extract campaign content as files and deliver them as a downloadable archive with filename mapping to the corresponding migrated Campaign/Deal. The customer's admin re-uploads content to Pipedrive or attaches it manually to the relevant Deal. Email templates do not migrate as Pipedrive email templates due to template structure incompatibility.