LeanData and Default at a glance
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.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. - 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 BookIt in Default
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.1
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.
2
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.
3
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.
4
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.
5
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.
6
Test and publish
Select Test, then Run Test with a test Lead for each path. Then select Publish, and
turn on the deployment switch so the status reads Live.
Move from LeanData to Default step by step
1
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.
2
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.
3
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.
4
5
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.
6
Rebuild each routing graph as a workflow
Build 1 workflow for each LeanData graph, as in
Rebuild a LeanData Lead router. Use
CRM Record Updated for graphs that reroute existing records.
7
Rebuild BookIt
Install the Pixel, add your forms with Catalog forms, and map their fields. See
Set up the Pixel and Forms SDK. Create events for your meeting types, then
build Form Submission workflows that end in Display Scheduler, and Extension workflows
for handoffs.
8
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.
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.