> ## Documentation Index
> Fetch the complete documentation index at: https://docs.os.default.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch from LeanData to Default

> Migration guide from LeanData to Default: how FlowBuilder graphs, Lead-to-Account matching, Round Robin pools, territories, and BookIt map to Default, the setup steps in order, and what has no direct equivalent.

Switching from LeanData to Default means rebuilding your LeanData FlowBuilder graphs as Default
workflows, your Round Robin pools as queues and routing policies, and your BookIt scheduling as
Default events. Default connects to Salesforce or HubSpot and runs matching, routing, and booking in
the same workflow.

This guide is for admins. Default does not import LeanData graphs, pools, or territories, so plan to
rebuild them and switch over 1 graph at a time.

## LeanData and Default at a glance

| LeanData | What it does in LeanData | Where it lives in Default |
| - | - | - |
| **Router** and **FlowBuilder** | A no-code, visual routing graph for Leads, Contacts, Accounts, Opportunities, and Cases in Salesforce. | A [workflow](/workflows): 1 trigger, then nodes that match, branch, route, and update records. |
| **Matching** (Lead-to-Account) | Relates Leads to Accounts with fuzzy matching, filters, and tiebreakers. | The **Match Record** node. There is no separate matching engine. |
| Round Robin pools | Groups of users that receive records in turn. | [Queues](/queues) and [routing policies](/policies), used by the **Round-Robin** node. |
| Territory routing | Routes records by territory in a router graph. | [Rules of Engagement](/rules-of-engagement) rulesets that choose a queue or user. |
| **Tagging** | Updates fields on a matched Lead with data from the Account. | **Update Record** after **Match Record**. |
| **BookIt** | Scheduling from forms, handoffs, and booking links. | [Events](/events), the **Display Scheduler** node, and the [Chrome extension](/chrome-extension). |

## LeanData FlowBuilder nodes in Default

A LeanData routing graph and a Default workflow have the same shape: an entry point, decisions, and
actions. This table maps the common LeanData nodes to Default nodes.

| LeanData node | What it does in LeanData | Default node |
| - | - | - |
| **New Entry** node | Starts routing for new records as they are created in Salesforce, for **All Leads**, **None**, or **Include the Leads below**. | **CRM Record Created** trigger, with an optional **Condition**. See [Triggers](/workflows/triggers). |
| Updated Entry node | Starts routing for existing records. | **CRM Record Updated** trigger, with an optional **Condition**. |
| Branch and True-False decision nodes | Send the record down different paths, by Yes/No questions or by several answers. | **Multi-Branch**. Branches run in order, and the **Else** branch catches the rest. See [Logic and timing nodes](/workflows/steps-logic-timing#multi-branch). |
| **Lead-to-Account Match** node | Finds Accounts for the routed Lead with fuzzy matching and **Filters**, then picks 1 with the **Tiebreakers** under **Prioritize Matched Accounts**. | **Match Record** on the Account. **Match Details** holds the conditions, and **Prioritize matched records by** picks 1 record when several match. |
| **Route to Matched Account** node | Assigns the record to the **Matched Account Owner**, a custom user field, an **Account Team**, or an **Owner Mapping**. | **Update Record** on the **Match** branch, with the owner field set to the matched Account's owner. |
| **Round Robin** node | Assigns the record to a member of a Round Robin Pool. | **Round-Robin**, then **Update Record** to write the owner. |
| Route to Territory and Route to ETM Model nodes | Assign records by territory. The ETM node uses your Salesforce Enterprise Territory Management model. | **Rules of Engagement**, with 1 rule for each territory. |
| **Convert Lead** node | Converts a Lead into a Contact under a matched Account, and can create an Opportunity. | **Convert Lead**, with **Account to merge into (optional)** set to the matched Account. |
| Email, Slack, or Teams alerts | Notify people when a record routes. | **Send Slack Message** or **Send Internal Email**. See [Notification nodes](/workflows/steps-notifications). |
| Actions such as Outreach sequences after assignment | Start follow-up in another tool. | [Sequencing nodes](/workflows/steps-sequencing) for Apollo, Outreach, Salesloft, Amplemarket, Smartlead, Gong Engage, and HubSpot Sequences. |

## Lead-to-Account matching in Default

Default matches a lead to an account with the **Match Record** node, inside the workflow. Default
has no separate matching engine.

* **Domain matching:** set **Record** to **Account**, choose **Website** as the field and
  **domain matches** as the operator, and compare it with the lead's email using
  **Domain from email**. The operator ignores `www.`, paths, and subdomains, handles country
  suffixes, and never matches public email domains. See
  [Match an account by company domain](/workflows/steps-crm#match-an-account-by-company-domain).
* **Tiebreakers:** when several accounts match, **Prioritize matched records by** applies your rules
  in order.
* **Branches:** the node follows **Match** or **No Match**, so a matched lead can go to the account
  owner and an unmatched lead can go to a territory ruleset or a queue.
* **Tagging:** on the **Match** branch, an **Update Record** node can copy fields from the matched
  Account onto the Lead.

## LeanData Round Robin pools in Default

| LeanData Round Robin | Default |
| - | - |
| Round Robin Pool | A queue. Its members, weights, and active state live on the queue. |
| **Count-Based** pool, lowest count gets the next record | **Take turns equally**: effective assignments divided by weight, and the lowest wins. |
| **Order-Based** pool, assignment in turn order | **Least recent assignment**: the member assigned least recently wins. |
| Weighting | **Enable weighted distribution** on the policy, then each member's **Weight** in the queue. |
| Calibration, including Auto-Calibrate for new members | Calibration on the queue member: **Calibrate to avg**, **Calibrate to max**, or **Custom**. |
| Schedules: working hours, holidays, and vacations | The policy's **Availability** tab skips members who are out of office, and optionally members who are busy. Members set out-of-office blocks in Default or on their calendar. |
| Count reset period | **Assignment reset schedule**: **Never**, **Monthly**, or **Quarterly**. |
| **No Round Robin Members Available** edge | The **Round-Robin** node fails when no member is eligible. The run log shows why. |
| Audit Logs, Routing Insights, and Deployment History | Workflow [run logs](/workflows/run-logs), **Routing** → **Assignments** with the scores behind each decision, and a new policy version for every policy edit. |

## LeanData BookIt in Default

| LeanData BookIt | Default |
| - | - |
| **BookIt for Forms**: routes a form submission and shows the rep's calendar | The Pixel picks up your existing form, and a workflow with the **Form Submission** trigger routes the lead and shows a **Display Scheduler** node. See [Connect a scheduler to your form](/forms/scheduler). |
| **BookIt Handoff**: suggests the right colleague for a sales development rep (SDR) to book with | A workflow with the **Extension** trigger. The rep runs it from the Chrome extension on a Gmail, Salesforce, or HubSpot page. |
| **BookIt Links**: personal and team booking links, including round robin | A **Quick event** for personal links, and a **Team event** with a queue as host for round robin. Each event has **Permanent** and **Expiring** booking links. |
| Meeting types, reminders, and invites | [Events](/events) and message templates in [Messages](/scheduling-messages), sent by email or SMS. |
| **BookIt API** and **BookIt MCP** | The [public API](/api/route-and-book) runs a routing workflow and books a meeting. The [MCP server](/mcp-server) is in beta. |

## Rebuild a LeanData Lead router as a Default workflow

This example rebuilds a common Lead router in Salesforce. New Leads that match an Account go to the
Account owner. Other Leads go through a territory ruleset, and anything the ruleset cannot place
goes to Revenue Operations for review.

<Steps>
  <Step title="Start from new Leads">
    In **Workflows**, create a workflow and add the **CRM Record Created** trigger. Set **CRM** to
    **Salesforce** and **Record** to **Lead**. Add a **Condition** if only some Leads should route,
    the way the New Entry node's filter does.
  </Step>

  <Step title="Match the Lead to an Account">
    Add **Match Record** with **Record** set to **Account**. Under **Match Details**, compare
    **Website** with the Lead's email using **domain matches** and **Domain from email**. Add
    tiebreakers under **Prioritize matched records by**.
  </Step>

  <Step title="Route matched Leads to the Account owner">
    On the **Match** branch, add **Update Record** for the Lead. Set the Lead's owner field to the
    matched Account's owner. Add any Account fields you copy onto the Lead, as Tagging did.
  </Step>

  <Step title="Route unmatched Leads by territory">
    On the **No Match** branch, add **Rules of Engagement** with your territory ruleset. Connect
    **Resolved** to an **Update Record** node that sets the Lead's owner field to the resolved user.
  </Step>

  <Step title="Handle Leads no territory covers">
    Connect **Else** to **Send Slack Message** for your Revenue Operations channel, or to a
    **Round-Robin** node with a catch-all queue and an **Update Record** node.
  </Step>

  <Step title="Test and publish">
    Select **Test**, then **Run Test** with a test Lead for each path. Then select **Publish**, and
    turn on the [deployment switch](/workflows#the-enabled-switch) so the status reads **Live**.
  </Step>
</Steps>

<Warning>
  A workflow test performs real actions. It updates Salesforce records and counts routing
  assignments. Use test Leads.
</Warning>

A **Rules of Engagement** node that chooses a queue also picks the member from it, so do not add a
**Round-Robin** node after it for the same Lead.

## Move from LeanData to Default step by step

<Steps>
  <Step title="Connect Salesforce">
    Select **Settings** in the sidebar, then **Integrations** under **Workspace Settings**, and
    connect Salesforce. Install the Default managed package for all users first. See
    [Salesforce](/settings/integrations/salesforce).
  </Step>

  <Step title="Invite your team and map Salesforce users">
    In **Settings** → **Users**, select **Invite People**. Then add each rep's Salesforce User ID, so
    Default can write them as record owners. See [Users](/settings/users).
  </Step>

  <Step title="Connect calendars if you used BookIt">
    Each member who takes meetings connects Google Calendar or Outlook Calendar and sets working hours.
    If your team meets on Zoom, an admin connects Zoom once for the workspace. Google Meet and
    Microsoft Teams links come from each member's own calendar connection. See
    [Member onboarding](/member-onboarding).
  </Step>

  <Step title="Rebuild Round Robin pools as queues">
    In **Routing** → **Policies**, select **Create Policy** and include **Objects** in
    **Assignment Units**, plus **Meetings** for booking. In **Routing** → **Queues**, select
    **Create Queue** for each pool and add its members. See [Policies](/policies) and
    [Queues](/queues).
  </Step>

  <Step title="Rebuild territories as a ruleset">
    In **Routing** → **Rules of Engagement**, select **New ruleset**. Declare the Salesforce fields your
    territories use under **Manage sources**, add 1 rule for each territory, order narrow rules above
    broad ones, and select **Publish**. See [Rules of Engagement](/rules-of-engagement).
  </Step>

  <Step title="Rebuild each routing graph as a workflow">
    Build 1 workflow for each LeanData graph, as in
    [Rebuild a LeanData Lead router](#rebuild-a-leandata-lead-router-as-a-default-workflow). Use
    **CRM Record Updated** for graphs that reroute existing records.
  </Step>

  <Step title="Rebuild BookIt">
    Install the Pixel, add your forms with **Catalog forms**, and map their fields. See
    [Set up the Pixel and Forms SDK](/pixel-sdk-setup). Create events for your meeting types, then
    build **Form Submission** workflows that end in **Display Scheduler**, and **Extension** workflows
    for handoffs.
  </Step>

  <Step title="Switch over 1 graph at a time">
    When a workflow passes its tests, publish it and set it live. At the same moment, stop the
    matching LeanData graph from taking those records. LeanData's documentation describes setting the
    New Entry node to send **None** into the workflow, which stops new Leads from routing there. When
    2 tools route the same record, they overwrite each other's owners.
  </Step>
</Steps>

## What does not carry over from LeanData

* **Configuration.** Default has no importer for FlowBuilder graphs, Round Robin pools, territory
  routing, or BookIt meeting types. You rebuild them in Default.
* **Routing history.** Audit logs and routing history stay in LeanData. Default starts its own
  assignment records from the first workflow run.
* **Microsoft Dynamics 365.** Default's CRM integrations are Salesforce and HubSpot.
* **Capping.** Default has no time-based or conditional cap on assignments for a rep.
* **Best-Fit Assignment and Next-Up.** Default has no attribute-based assignment mode and no manual
  choice of the next rep. On a new or reset queue, an admin can drag members to set the first order.
* **Account Team and Owner Mapping.** Default writes owner fields and other user fields with
  **Update Record**. It has no built-in option to assign through Salesforce Account Teams or an owner
  mapping table.
* **Enterprise Territory Management.** Default has no node that routes from a Salesforce Enterprise
  Territory Management model. Territories live in Rules of Engagement rules.
* **Scheduled routing jobs.** Default workflows start from a trigger such as a CRM record change, a
  form submission, an incoming webhook, or an API call. There is no scheduled trigger.
* **Service-level agreement (SLA) alerts.** Default has no SLA setting that alerts when a rep does
  not act on a record.
* **Case routing counts.** A Default queue counts an assignment when the owner is written to a
  Salesforce Lead, Contact, Account, or Opportunity. An owner written on a Case or a custom object
  does not count toward round robin.
* **Microsoft Teams alerts.** Default posts notifications to Slack and emails your team. Microsoft
  Teams is supported for meeting links only.
* **View, Attribution, and Buying Groups.** These LeanData products have no Default equivalent.
* **Routing Links with their own form.** Default doesn't design or host forms, so there is no hosted
  form page behind a link. Put the form on your website, either one you add with **Catalog forms**
  or one you create in Default with **Create new** → **New form**, and route it with a
  **Form Submission** workflow. See
  [Create a form in Default](/forms/your-forms#create-a-form-in-default).

Related: [Default vs LeanData](https://www.default.com/comparison/leandata)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.