Migrate from WayMore to Pipedrive

WayMore Contact records export as CSV with name, email, phone, behavioral data, and custom field values. We map them to Pipedrive Person records using email as the deduplication key. Custom field values on WayMore contacts require pre-creation of corresponding Pipedrive custom fields before import. Any contacts marked as unsubscribed or suppressed in WayMore have the email opt-out status preserved in Pipedrive's Person opt_in_status or a custom field.

WayMore Company records map directly to Pipedrive Organization records. We use the company domain as the Organization Website field and as a secondary deduplication key alongside company name. If WayMore contacts have a primary company association, we resolve the Organization record first so that the Person-Organization link is satisfied at insert time.

WayMore tags applied to Contacts and Companies export as a flat list per record. We transform these into Pipedrive Person Tag or Organization Tag associations during import. The customer chooses whether tags migrate as Pipedrive native tags or as multi-select picklist values on a custom field, depending on how the sales team intends to use them for segmentation.

WayMore dynamic segments defined by behavioral rules cannot replicate as dynamic rules in Pipedrive. We export the current contact membership of each WayMore segment as a static tag list and associate those contacts with a Pipedrive tag named for the segment. The static list preserves segment membership at cutover but will not auto-update. We document the original segment rule definitions in the handoff inventory.

WayMore email campaign records (subject, content, sending history) migrate as Pipedrive Activity records of type task linked to the Person or Organization. Campaign metadata including send date, open rate, and click rate export as custom fields on the Activity record. We do not migrate email body content as templatable Pipedrive emails because Pipedrive email templates are rebuilt manually in the platform's template editor.

WayMore SMS campaign records and message templates export as CSV. We map them to Pipedrive Activity records linked to the Person. Opt-out status per contact is preserved to maintain SMS compliance. SMS campaign sending history migrates as custom fields on the Activity record.

WayMore push notification campaign records and subscriber lists migrate as Pipedrive Activity records. Device tokens and subscriber identifiers are platform-specific and do not transfer between systems. We document the active push notification subscriber count at cutover for the customer to re-establish in Pipedrive's notification integration.

WayMore automation workflows with triggers, conditions, and delays cannot migrate as functional automation in Pipedrive. We export the complete workflow definition including step sequence, trigger events, condition branches, and action types as structured JSON documentation. Pipedrive's workflow automation (trigger-and-action format) is available from the Advanced plan at $24.90 per user per month; the customer rebuilds using our documented definition as the specification.

WayMore chatbot AI flows use a visual decision-tree builder. We export the flow structure including decision nodes, response branches, and integration points as a structured document. Pipedrive's LeadBooster add-on includes chatbot capabilities but chatbot flows do not transfer automatically. We deliver a chatbot flow map for the customer's admin to rebuild in Pipedrive's LeadBooster Playbooks editor.

WayMore lead capture forms and their field configurations export as form definitions. We document form-to-automation connections separately since those automations do not migrate. Pipedrive Web-to-Lead forms or Experience Cloud forms serve as the replacement lead capture mechanism. The customer configures new forms in Pipedrive using the field mapping from our documentation.