Migrate your Flowlu data

Projects serve as the top-level work container in Flowlu, holding tasks, milestones, time entries, expenses, and invoices. We preserve the full project card data including stage, deadline, project manager assignment, and financial widgets. Workflow-based projects display on the Project Workflow board and we map that attribute correctly.

Tasks are the granular work unit inside Projects. We map task name, description, status, assignee, due date, planned and actual time, and custom field values. Dependencies between tasks are preserved as a linked field pair. Subtasks are treated as nested tasks under their parent task.

Agile Projects use sprints, backlogs, and an issue tracker separate from standard Projects. We map sprint assignments, backlog rank, issue priority, and story points where present. The sprint-to-sprint burndown history requires aggregation at migration time.

Opportunities sit inside Pipelines and carry stage, amount, probability, expected close date, and custom fields. We map these as Deals or Opportunities in the destination. Custom fields on Opportunities require value mapping because Flowlu supports list-based custom fields that may not map directly to free-text or picklist fields in the target.

Contacts store name, email, phone, company association, lifecycle stage, and custom properties. We handle deduplication at migration time using email as the primary key. Custom fields on Contacts are mapped field-by-field, and list-type custom fields are expanded into multi-select or tag fields in the destination where supported.

Companies are separate record types that Contacts link to. We map company name, industry, website, address, and any custom fields. The relationship between Contact and Company records is preserved by mapping the Company ID reference on each Contact.

Pipelines define the sales stages visible on the CRM board. We map the pipeline name, stage names, stage order, and stage-specific probability values. Active deals are migrated with their current stage intact.

Individual stages within a Pipeline are migrated with their display order and probability percentages. Stages are tied to their parent Pipeline so deal placement in the destination reflects the original board layout.

Invoices contain line items, tax rates, payment status, and issuer details. We map invoice date, due date, line items, totals, and payment status. Historical invoices may reference closed Projects or archived Companies; we flag these as potentially orphaned references and give the customer the choice to remap or skip.

Flowlu Knowledge Base articles store title, body content, category assignment, and optional custom fields. We map article content and category. Articles linked to specific Knowledge Base sections may require destination-side section creation before import.

Custom Fields attach to Projects, Tasks, Opportunities, Contacts, Companies, Knowledge Base items, and more. Each Custom Field has a type (text, number, date, list, checkbox, etc.) and may be required or read-only. We extract the full custom field schema during scoping and map each field type to the closest equivalent in the destination CRM.

Time entries record hours logged against Tasks or Projects, with user assignment and optional descriptions. We map entry date, duration, user, task/project reference, and billable flag. Billable time entries are cross-referenced with Invoices where applicable.

Flowlu Users have roles (Admin, Manager, Member) and can be grouped into Teams. We map user email, name, role, and team membership. Owner assignment on records is migrated by email lookup; if a user does not exist in the destination, we flag it for the customer to resolve.