Migrate from Flowlu to Pipedrive

Flowlu Contacts map to Pipedrive Persons using email as the dedupe key. First name, last name, phone, company association, lifecycle stage, and custom properties migrate directly. Pipedrive Persons do not have a native lifecycle stage property, so Flowlu lifecycle stage values migrate to a custom Person field for reporting. Duplicate resolution uses email as the primary key with an optional secondary check on phone number.

Flowlu Companies map to Pipedrive Organizations. Company name, industry, website, address, and custom fields migrate. The relationship between Flowlu Contact and Company (stored as a linked record) is preserved in Pipedrive by resolving the Organization UUID at Person import time and setting the org_id field on each Person record.

Flowlu Opportunities map to Pipedrive Deals. Stage, amount, probability, expected close date, owner, and custom fields transfer directly. Flowlu's pipeline assignment resolves to a Pipedrive Pipeline ID during import. Deals without a linked Company in Flowlu are imported as unlinked Deals in Pipedrive with a custom note field recording the original Flowlu company reference for manual linking post-migration.

Flowlu Pipelines map to Pipedrive Pipelines. The pipeline name, display order, and active/archived status transfer. Pipedrive allows multiple pipelines from the Essential tier onward, matching Flowlu's multi-pipeline capability on paid plans. We preserve pipeline-level settings that affect deal visibility and reporting.

Flowlu Pipeline Stages map to Pipedrive Stages within their parent Pipeline. Stage display name, order, and probability percentage transfer. Flowlu stages without a probability value receive a default probability that we set based on the stage's position in the pipeline. Probability values are stored as integers in Pipedrive API v2, requiring rounding of Flowlu decimal values.

Flowlu Custom Fields on Contacts, Companies, Opportunities, and Projects map to Pipedrive Custom Fields on Persons, Organizations, and Deals respectively. We extract the complete Flowlu custom field schema per object during scoping, then pre-create Pipedrive custom fields of matching types (text, number, date, dropdown, checkbox, phone, email) before data import begins. Flowlu list-type fields map to Pipedrive dropdown fields; Flowlu multi-select lists require a custom text field or separate configuration depending on Pipedrive plan support.

Flowlu Users map to Pipedrive Users by email match. We extract role information from Flowlu (Admin, Manager, Member) and preserve it in a custom Pipedrive field for the customer's admin to map to Pipedrive role assignments. Active Pipedrive Users must exist before Deal and Person import so that owner_id references are valid. Users in Flowlu without corresponding Pipedrive accounts enter a reconciliation queue.

Flowlu Time Entries (hours logged against Tasks or Projects) have no native Pipedrive equivalent. We map billable Time Entries to Pipedrive Note records linked to the related Deal using the Deal UUID. Each Note records the date, duration, user, task description, and billable flag as plain text in the Note body. Non-billable Time Entries are excluded unless the customer requests they be preserved as Activity records. Projects and Tasks that Time Entries reference are flagged as unmapped scope in the handoff document.

Flowlu Invoices (line items, tax rates, payment status, issuer details) have no Pipedrive equivalent. We extract invoice metadata as a CSV export with Deal references and deliver it to the customer for import into their accounting tool (QuickBooks, Xero, or Stripe) or manual Pipedrive entry. Invoice PDF files are exported as file attachments and linked to the corresponding Deal records via a custom field. Historical payment status is preserved in a Pipedrive custom field for deal closure reference.

Flowlu Knowledge Base articles have no Pipedrive equivalent. We extract article titles, body content, and category assignments as a structured export. The customer receives a Markdown-formatted archive of all articles organized by Knowledge Base section. Article-to-record linkage (e.g., articles linked to specific Projects or Companies) is preserved in the export as a reference field, allowing the customer to re-associate content manually in a wiki or knowledge base tool post-migration.

Flowlu Projects and their nested Tasks, Milestones, and Agile boards have no Pipedrive equivalent. We extract project card data (name, stage, deadline, owner, budget, custom fields) as a structured export. Task data is extracted with parent-project references preserved. The customer receives a project inventory document with task counts, assignee assignments, and milestone dates for manual import into a project management tool (Asana, Monday.com, ClickUp) or for use as a rebuild reference in Pipedrive Activities.

Flowlu Workflows operate across Projects, Tasks, and CRM objects and do not carry over to Pipedrive's Automation Builder, which uses a different trigger-condition-action model. We document every active Flowlu workflow with its trigger type, conditions, and actions as a written handoff for the customer's admin to rebuild in Pipedrive or a third-party automation tool. This documentation includes workflow name, object scope, trigger events, condition branches, and recommended Pipedrive Automation Builder equivalent steps.