The object that matters.
Search inventories and inspect the settings behind each name.
Migrator Policy migration services
Built by Braxton-Grant.
Control the change.
Simplify the path from test to production.
Compare iboss tenants, promote supported policy objects, and verify the result. Bring order to changes across your environments—with automated tools and expert guidance from BGT.
01 / TESTBuild & compare
- Inspect source inventories
- Review policy details
- Compare selected settings
02 / STAGINGCheck & prepare
- Resolve dependencies
- Review proposed changes
- Prepare the destination
03 / PRODUCTIONPromote & verify
- Promote supported objects
- Read back destination settings
- Record the outcome
Braxton-Grant automation toolsOne controlled workflow.
Policy migration / Change control / Verification / Audit trail
Use the same workflow between tenant pairs at each stage. Your team reviews changes, manages approvals, and confirms policy behavior.
Less manualre-creation
More deliberatechange control
Repeatablepreparation
Clearer auditevidence
Stronger operationalhandoffs
The product in context
Two tenants.
One clear view of the work.
Keep source and destination in view as you inspect policy details, compare configurations, and prepare a change.
The meaningful differences.
Review configuration differences and explore the underlying JSON.
The next informed step.
See which dependencies are ready and which need attention.
Controlled promotion
Move policy forward.
Keep control of the change.
Use iboss Migrator within your change process, whether you are promoting a tested configuration or aligning selected settings across environments.
- 01 / COMPARE
Establish a baseline.
Connect a source tenant or load an export. Authenticate to the destination and review inventories and differences.
- 02 / CHECK
Resolve prerequisites.
Inspect the selected object and its dependencies. Use the findings to prepare the destination.
- 03 / PROMOTE
Apply the selected change.
Use the destination mappings and settings you reviewed to carry supported objects forward.
- 04 / VERIFY
Confirm the result.
Read back destination settings, check that the change persists, and record the outcome.
Support recovery as well as delivery. Rollback handling helps the team recover when a migration or verification fails. Keep verification and acceptance checks in your change process.
Export. Import. Diff.
Keep a baseline.
Make change visible.
Export tenant configuration for review and handoff. Bring it back into the workspace to inspect individual objects, compare saved configurations, or review differences against a live tenant.
- Capture a reference. Retain configuration evidence and collection status.
- Inspect the details. Explore differences and JSON views.
- Collect from the command line. Make exports part of recurring reviews.
A SAVED SOURCE. A FAMILIAR WORKFLOW.
Migrate from an export.
Load an NDJSON export, select supported objects, and promote them into an authenticated destination—without reconnecting to the original source tenant.
Export→Review→Promote
- Choose individual objects
- Preview settings and destination dependencies
- Verify and record the result, tied to the export
An audit trail for the work
Give the next reviewer
more than a recollection.
Carry configuration changes and migration outcomes into change tickets, troubleshooting, and operational handoffs.
Use tenant hygiene reports to investigate hidden name conflicts, migration fragments, and other issues that can obstruct a change.
- Who
- Authenticated user and selected account.
- Where
- Source and destination tenant identities.
- What
- Action, object type, and selected objects.
- Outcome
- Committed, rolled back, or requiring investigation.
Know the scope before you move
Selected objects.
Reviewed dependencies.
Coverage depends on the object, its configuration, and the product release. BGT will confirm the supported path for your environment before migration.
Resources & organization
Resources, Resource Categories, and Tags.
Policy selections
Category-Based, selected Resource-Based, and Private Access policies.
Supporting settings
Allow/block list entries, Web Category states, and Policy Layer shells.
Proxy Rules: comparison and diagnostics are available; the migration workflow is not yet available. Confirm object and dependency coverage with BGT.
Questions customers ask
Put the workflow
to work for you.
Can we compare exports without changing a tenant?
Yes. Load an NDJSON export to inspect its objects and compare it with another export or a live tenant. Selective migration is a separate step into an authenticated destination.
How do readiness checks help?
Review the dependencies your selected object needs, prepare destination objects, and refresh the comparison. The findings help your team resolve gaps before promotion.
Can we use this across multiple tenants?
Use the same compare, prepare, and promote workflow between tenant pairs. Saved exports also provide a reusable source for supported objects across environments.
How does this fit our approvals and acceptance process?
Use comparisons and readiness checks during review, then carry verification results and audit evidence into your existing process. Your team manages approvals and confirms intended policy behavior in the destination.
See it with your use case
Bring the policy. We’ll walk through the path.
Bring a representative policy and the tenants you manage. We’ll review comparison, migration from live tenants or exports, and destination preparation for your workflow.
Let’s move your mission forward.
The right technology.
The right people. Your next step.
Economically Disadvantaged Women-Owned Small Business