Migrate Configuration
The Migrate tab lets you copy scoring configuration from one Organizational Unit (OU) to another. This is useful when you have a template OU with a proven scoring model and want to replicate it to a new OU without rebuilding everything from scratch.
When to Use Migration
- Launching a new OU: You have an existing OU with well-tuned rules, levels, and segments, and want to use the same configuration as a starting point for a new team or region.
- Standardizing configuration across OUs: Your organization has standardized scoring logic that should apply to multiple OUs.
- Promoting from a staging OU: You maintain a staging OU for testing and want to promote validated changes to your production OU.
Migration copies configuration — it does not move or delete anything from the source OU.
What Can Be Migrated
| Configuration Type | Examples |
|---|---|
| Filters | Inorganic activity suppression rules |
| Mapping | Profile and account field mappings |
| Scoring | Engagement rulesets and rules, profile rulesets, account rulesets, decay rules |
| Levels | Engagement levels, profile levels, account levels |
| Segments | Segment definitions and their rules |
| Triggers | Milestone triggers, sequence triggers |
How Migration Works
Migration uses a four-step wizard:
- Source — Select the OU you want to copy configuration from
- Items — Choose which specific items to migrate
- Target — Select the destination OU and preview what will be copied
- Done — Review results
Step 1: Select Source OU
Choose the Organizational Unit you want to copy configuration from. You must have access to at least two OUs to use the migration feature.
If no other OUs are available, you will be prompted to create one first.
Step 2: Select Items
kenbun loads all configuration items from the source OU, organized by type:
- Filters: Suppression rules for filtering out inorganic activity
- Mapping: Profile and account field mappings
- Scoring: All rulesets (engagement, profile, account) and decay rules
- Levels: Engagement, profile, and account level thresholds
- Segments: Segment definitions
- Triggers: Milestone and sequence triggers
For each category, you can:
- Select All or Deselect All within a category
- Select individual items using the checkboxes
If the source OU has no configuration items, you will see a message indicating there is nothing to migrate.
Step 3: Preview and Select Target OU
Before executing the migration, kenbun shows a preview of what will be copied. The preview is split into two sections:
Items to Copy: The items you explicitly selected.
Auto-Included Dependencies: Additional items that must be copied along with your selection to maintain consistency. For example, if you selected a segment whose rules reference a specific profile level, that level is automatically included.
Select the target OU from the dropdown. The source and target must be different Organizational Units — kenbun will not allow you to migrate an OU to itself. If an item with the same configuration already exists in the target OU, it will be listed as Skipped in the results rather than duplicated.
Click Execute Migration to begin.
Step 4: Review Results
After the migration completes, you will see a summary organized into three groups:
| Group | Meaning |
|---|---|
| Copied | Items successfully created in the target OU |
| Skipped | Items that already existed in the target OU and were not changed |
| Errors | Items that could not be copied, with a reason |
Items in the Skipped and Errors groups are not modified or deleted in either OU.
What Migration Does Not Cover
- Lead data: Leads, events, and scores are never copied between OUs. Migration is configuration-only.
- Integration credentials: Slack, HubSpot, and other integration connections are not migrated. Each OU must be connected to its integrations independently.
- Team members: OU membership is managed separately in Settings > Organization.
Best Practices
Test in a Staging OU First
If you are making significant changes to scoring rules, test them in a staging OU before migrating to production. This lets you validate the configuration without affecting live scoring.
Review Auto-Included Dependencies
The preview step shows which items were automatically added to your migration because they are required by the items you selected. Review this list carefully — you may be copying more than you intended.
After Migration
After completing a migration, navigate to the target OU and verify:
- Levels are configured correctly and cover the expected score ranges
- Scoring rules are enabled and have the correct weights
- Triggers are in the correct state (active or paused)
- Segments show the expected lead counts after membership is recalculated
Accessing Migration
Navigate to Govern > Migrate to access the migration wizard. You must have administrator access to your Organizational Units to use this feature.
Related Features
- Organizational Units — Manage your OUs and their settings
- Scoring Rules — Understanding the rules that power lead scoring
- Levels — Configure engagement, profile, and account levels
- Segments — Segment definition and management
- Triggers — Automate actions based on scoring conditions