Migrate from Delivra to Pipedrive

Delivra Contact records map directly to Pipedrive Person records. Core properties including email address, first name, last name, phone, address fields, and custom fields migrate as typed Pipedrive fields. The email address serves as the dedupe key during import. Subscription status and GDPR consent flags from Delivra map to the HasOptedOutOfEmail field on the Person record for compliance continuity. Any Delivra contact property that has no direct Pipedrive equivalent becomes a custom field created before migration begins.

Delivra stores company data as properties on the Contact record rather than as a separate object. We extract company-related fields (company name, industry, website, address) and create Pipedrive Organization records, then link the Person record to the Organization via a Person-to-Organization relationship. If the original Delivra contact had no company name, we create an Organization only when a company name exists to avoid orphan organizations.

Delivra Custom Tables with 1:many or many:many relationships to Contacts cannot map directly to Pipedrive because Pipedrive has no native custom object support. We denormalize these relationships into custom fields on the linked Person or Organization record. For 1:many tables (one contact has multiple related rows), we flatten to multiple custom fields (field_1, field_2, field_n) or to a long-text field with pipe-delimited values. For many:many tables, we store the related table name and key in a custom field and deliver a written schema map so the customer's admin can reconstruct the relationship in an external tool or a linked table if needed.

Delivra Campaign records include name, status, targeting criteria, and associated content metadata. We map campaign name and status to a Pipedrive Activity with type Note, linked to the relevant Person and Organization records that were in the campaign audience. The original campaign targeting criteria is stored as a custom note body field. Email content within campaigns migrates as Activity notes; we do not rebuild the visual email layout in Pipedrive since Pipedrive is not an email marketing platform.

Delivra Lead Scoring assigns point values to contact attributes and behaviors. We export the numeric score and the scoring model rules. The score migrates as a custom integer field on the Person record (lead_score__c). The scoring model rules are documented in the handoff inventory so the customer's Pipedrive admin can re-implement a similar scoring model using Pipedrive's custom field formulas or a third-party scoring tool.

Delivra tracks email opens, clicks, and engagement timestamps as properties on the Contact record and as separate engagement event records. We extract the most recent engagement date, total opens, total clicks, and last click URL as custom fields on the Person record. Historical engagement events migrate as Activity records with type Note and the engagement details stored in the activity body, linked to the Person record. Engagement data volume can be large (tens of thousands of events per contact); we batch and paginate using the Pipedrive API rate limits.

Delivra Segments are dynamic filter definitions applied to contact lists. Pipedrive does not have a native segment builder. We translate Delivra segment criteria to a set of Pipedrive Person custom fields and static tags. For each Delivra segment, we identify the matching contacts, apply a tag with the segment name to the Person record in Pipedrive, and document the original segment filter logic so the admin can recreate equivalent filtered views using Pipedrive's Person filter feature.

Delivra User accounts (email, name, role) map to Pipedrive User records. We extract user records and match by email address against the destination Pipedrive account's User table. Any Delivra User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role-based permissions from Delivra are documented for rebuild in Pipedrive's role and permission settings.

Delivra Automated Workflows built with visual triggers, conditions, and actions do not migrate as code to Pipedrive. We extract the full workflow logic including decision branches, time delays, action sequences, and entry/exit criteria. We deliver a written inventory document that maps each Delivra workflow to an equivalent Pipedrive Automation Goal and documents the trigger, conditions, and actions in Pipedrive's terminology. The customer's admin rebuilds the automations in Pipedrive after go-live.

Delivra Email Templates built in the drag-and-drop editor do not transfer as functional templates to Pipedrive because Pipedrive is not an email marketing platform. We extract template content (HTML body, subject line, images as base64 or external URLs) and store it as an Activity note on a designated template Organization or Person record. The customer's admin references the Activity note to rebuild templates in their chosen email marketing tool. Complex templates with conditional content require manual reconstruction.

Delivra web forms and landing pages built in the visual editor do not migrate as code. We extract form field definitions, field types, and landing page URLs for documentation purposes. The customer rebuilds forms in Pipedrive Web Forms or a third-party form tool (Typeform, JotForm, HubSpot Forms) and updates their website integration accordingly. Landing pages require rebuild in a dedicated landing page tool.