Migrate from Floww.ai to Microsoft Dynamics 365 Sales

Floww.ai Contact records map directly to Microsoft Dynamics 365 Contact. Standard fields (FullName, Email, Phone, BusinessPhone, CompanyName) migrate 1:1. Floww.ai custom Contact properties migrate as typed fields on the Contact entity in Dataverse. Email address is used as the primary dedupe key during import to prevent duplicate Contact creation.

Floww.ai Lead records (distinct from Contacts in Floww.ai's data model) map to Dynamics 365 Lead. Lead source, status, rating, and any custom categorization fields migrate to the corresponding Lead entity fields in Dataverse. We preserve the Floww.ai lead categorization as a custom field for audit and to support any downstream segmentation logic.

Floww.ai Company records map to Dynamics 365 Account. Company name maps to Account Name; domain fields map to Website. Account is created before Contact import so that the CustomerId (Account) lookup relationship is satisfied at the moment of Contact insert. The customer chooses whether to use Account as the primary organizational unit for Deals or to attach Deals directly to Contact records.

Floww.ai Deal records map to Dynamics 365 Opportunity. Deal value maps to EstimatedRevenue; expected close date maps to EstimatedCloseDate; owner assignment maps to OwnerId. The Deal's linked Pipeline and Stage are resolved during migration by matching Pipeline name to a Microsoft Dynamics 365 Sales Process and Stage to a Stage within that process. We create the Sales Process configuration before migration if it does not already exist in the destination org.

Floww.ai Pipelines (which support multiple concurrent pipelines with distinct stage sets) map to Dynamics 365 Record Types on Opportunity, each paired with a corresponding Sales Process that whitelists the relevant stage values. Stage order and naming conventions are reconciled against the Dynamics 365 stage model during configuration design. If the customer has three distinct business lines with different stage sequences, we create three Record Type and Sales Process combinations to preserve that structure.

Floww.ai Pipeline Stages map to Dynamics 365 Opportunity Stage values within the corresponding Sales Process. Stage probability percentages migrate from Floww.ai to Dynamics 365 StageProbability. Note that Floww.ai stage-level filters (which do not persist across navigation in the source platform) are documented as part of the configuration inventory rather than exported directly; we provide a written reconstruction plan for each stage filter that the customer's admin implements in Microsoft Dynamics 365 Sales Processes or Power Automate.

Floww.ai Activities (calls, emails, notes, scheduled tasks logged against Contacts and Deals) map to Dynamics 365 Activity records. Call activities become Task with TaskSubtype=Call; email activities become Email; notes become Annotation (note) records linked via Dataverse RegardingObjectId to the parent Contact, Account, or Opportunity. Activity timestamps (CreatedAt) map to ScheduledEnd for tasks and to ActualStart/ActualEnd for events. The Activity pointer to the linked Contact or Deal record is preserved as RegardingObjectId in Dataverse.

Floww.ai Custom Objects with one-to-many and many-to-many relationships map to Dataverse custom entities. We request a schema map from the customer before migration, pre-create the destination schema in Dataverse (including all custom columns, lookup relationships, and many-to-many intersect entities), then migrate records after the primary object migration completes. Many-to-many relationships in Floww.ai become Dataverse Many-to-Many relationships with a corresponding intersect entity; one-to-many relationships become Lookup columns on the child entity. The customer confirms the Dataverse entity naming convention during scoping.

Floww.ai Users referenced on Contacts, Deals, and Activities map to Dynamics 365 User records by email address match. Any Floww.ai Owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes. We do not migrate Floww.ai user roles or permissions; these are reconfigured in Dynamics 365 Security Roles and Teams post-migration.

Floww.ai Tags used for segmentation migrate as a text field on the relevant record (Contact or Deal) storing comma-separated tag values, or as a multi-select option set if the Dynamics 365 org supports that field type. The customer chooses the tag strategy during scoping. Tags used for Contact Hit List (telesales sequencing) require a separate rebuild plan in Microsoft Dynamics 365 Sales using Sales Process stages or a custom entity if the sequence logic is complex.