Migrate from Flowlu to Salesforce Sales Cloud

Flowlu Contacts map to Salesforce Contact with a direct field-to-field mapping: name, email, phone, company association, and lifecycle stage. Flowlu's company link resolves to Salesforce AccountId via a lookup by company name or domain during import. We run deduplication on email as the primary key. Custom fields on Contacts are extracted per the Flowlu custom field schema and pre-created as typed Salesforce fields before import. Any Flowlu list or picklist fields map to Salesforce picklist fields with matching values.

Flowlu Companies map directly to Salesforce Account. Hub name, industry, website, address, and all custom fields migrate 1:1. The Account record must exist before Contact import so that AccountId is available for the Contact-company lookup at insert time. We resolve the lookup by matching company name and domain from Flowlu to Salesforce Account.

Flowlu Opportunities map to Salesforce Opportunity with stage, amount, probability, expected close date, owner, and all custom fields preserved. Flowlu's pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. The pipeline stage name in Flowlu maps to the Opportunity StageName value in Salesforce. Custom fields on Opportunities (Flowlu's CRM objects with custom fields) migrate to custom Opportunity fields.

Flowlu's CRM pipelines map to Salesforce Opportunity Record Types. Each Record Type gets a corresponding Sales Process that whitelists only the relevant stage values. We create the Record Type and Sales Process in the Sandbox org first, validate with the customer, then deploy to production. Multiple Flowlu pipelines map to multiple Salesforce Record Types so that stage values stay scoped per line of business.

Individual stages within a Flowlu Pipeline map to Salesforce Opportunity StageName picklist values. Stage display order migrates, and stage-specific probability percentages map to StageProbability on the Sales Process. We round probability values to the nearest integer as Salesforce requires.

Flowlu Projects are a core data type with no native Salesforce equivalent. We map to a custom Project__c object if the customer licenses Salesforce (with Salesforce Projects or a custom object) or recommends a dedicated PM tool. Project card data including stage, deadline, project manager, and budget migrate. We deliver a written decision document during scoping that explains the three paths: custom Project__c object with Salesforce Tasks, migration to Jira or Asana with a link record, or drop. The customer chooses before schema creation begins.

Flowlu Tasks map to Salesforce Task with name, description, status, assignee, due date, planned and actual time, and custom field values. If Projects migrate to a custom Project__c object, we preserve the parent-project relationship as a Lookup field on Task (Project__c). Task dependencies are flagged as a custom field dependency_chain__c since Salesforce does not have a native dependency model.

Flowlu Invoices map to Salesforce Invoice if the org has Salesforce Billing enabled, otherwise to a custom Invoice__c object. We map invoice date, due date, line items, totals, payment status, and issuer details. Flowlu invoices may reference closed Projects or tasks; if the Project was not migrated to Salesforce, the WhatId on the invoice is set to the related Account and flagged for manual review. Tax rates and payment terms carry over as custom fields.

Flowlu Knowledge Base articles map to Salesforce Knowledge only if the destination org has Service Cloud with Knowledge enabled and the admin has configured Data Categories. Article title, body content, and category assignment migrate. Articles linked to specific Flowlu Knowledge Base sections are flagged for manual relinking because Salesforce Knowledge does not have an equivalent section structure. If Salesforce Knowledge is not available, we map to a custom Knowledge__c object and deliver a data map for the customer to configure Salesforce Knowledge post-migration if they add the license.

Flowlu Workflow automations do not migrate as code because Flowlu's object-triggered workflow model is structurally different from Salesforce Flow's record-triggered, scheduled, and screen flow variants. We extract a full JSON export of every active Flowlu workflow with its trigger conditions, actions, delays, and CRM object scope. We deliver a written inventory document mapping each Flowlu workflow to a recommended Salesforce Flow type (Record-Triggered Flow, Scheduled Flow, or Screen Flow) with a step-by-step rebuild guide for the customer's admin.

Flowlu Agile Projects use sprints, backlogs, and an issue tracker separate from standard Projects. We do not migrate Agile data to Salesforce because Salesforce has no Agile Sprint or backlog model. We extract sprint assignments, backlog rank, issue priority, and story points and deliver a written data map for migration to Jira or a dedicated Agile tool. Jira for Salesforce (by ServiceRocket) is an option for teams that want the backlog visible inside Salesforce.

Flowlu Custom Fields attach to Projects, Tasks, Opportunities, Contacts, Companies, Knowledge Base items, and Agile Issues. We extract the complete custom field schema per object type, including field type (text, number, date, list, checkbox, dropdown), required flag, and any conditional visibility rules. Each field is pre-created in Salesforce before data import begins. Mis-matched field types (Flowlu list fields vs Salesforce free-text) are flagged for manual review during scoping. Required field violations can block Salesforce inserts; we handle with either a temporary required-field override during migration or a manual review queue.

Flowlu Time Entries map to Salesforce Task records linked to the parent Project custom object (if applicable) and the relevant Task. We map entry date, duration in minutes, user by email lookup, task and project references, and the billable flag as a custom Task field billable__c. Billable time totals reconcile against Flowlu's time tracking report during validation.

Flowlu Users with roles (Admin, Manager, Member) and team memberships map to Salesforce User records by email match. Owner assignments on Contacts, Opportunities, and Tasks resolve via the User mapping. Any Flowlu User without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import proceeds.

Flowlu Tags stored as multi-checkbox properties on Contacts, Companies, or Opportunities map to Salesforce multi-select picklist fields. Tags used for classification migrate to Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping: multi-select picklist is simpler and works for most use cases; Topics require a Topic-enabled org.

Flowlu invoices can reference closed Projects or tasks that may not exist in Salesforce. We map the invoice header (date, due date, issuer, totals, payment status) and line items to Salesforce Invoice or a custom Invoice__c object. If the related Account exists in Salesforce, we link via AccountId. Line item references to Flowlu-only Projects or tasks are set to null and flagged for manual reconciliation post-migration.