Migration Guide
Migrate from uBlock Origin
Planning to transition from uBlock Origin to Ghostery? This guide helps IT administrators plan and execute a smooth migration.
Manifest V3 Deadline
Chrome is phasing out Manifest V2 extensions. uBlock Origin's full version will stop working in Chrome. Plan your migration now to avoid disruption.
Why Migrate?
Manifest V3 Compatibility
Chrome's transition to Manifest V3 significantly impacts ad blockers. Ghostery is built on Manifest V3 from the ground up, ensuring:
- Continued functionality as Chrome phases out Manifest V2
- No disruption to your ad blocking coverage
- Compliance with Google's extension platform requirements
Enterprise Support
- Dedicated enterprise support team
- Managed storage policies for centralized configuration
- Custom builds for specific requirements
- SLA-backed support options
Feature Comparison
| Feature | uBlock Origin | Ghostery |
|---|---|---|
| Ad Blocking | Yes | Yes |
| Tracker Blocking | Yes | Yes |
| Manifest V3 (Chrome) | Limited (uBO Lite) | Full Support |
| Enterprise Policies | Limited | Full Support |
| Disable User Control | No | Yes |
| Trusted Domains Policy | No | Yes |
| Skip Onboarding | No | Yes |
| Custom Filter Lists | Yes | Yes |
| Open Source | Yes | Yes |
| Enterprise Support | Community | Dedicated Team |
Migration Checklist
Test Before Deploying
Always test Ghostery with a pilot group before organization-wide deployment. This helps identify any site compatibility issues specific to your environment.
Pre-Migration
- Inventory current uBlock Origin deployments (browsers, platforms, policy settings)
- Identify any custom filter lists in use
- Document any sites currently whitelisted
- Determine Ghostery policy requirements (lockdown level, trusted domains)
- Test Ghostery in a pilot group
Migration
- Deploy Ghostery using your existing management tool (same method as uBlock Origin)
- Configure managed storage policies
- Add trusted domains (equivalent to whitelist)
- Remove uBlock Origin from force-install policies
Post-Migration
- Verify Ghostery is installed on all target devices
- Monitor helpdesk tickets for any issues
- Update documentation and runbooks
Policy Mapping
If you used uBlock Origin with custom configurations, here's how to map common settings:
| uBlock Origin Setting | Ghostery Equivalent |
|---|---|
| Whitelist/Trusted sites | trustedDomains policy |
| N/A | disableUserControl - lock down user access |
| N/A | disableOnboarding - skip setup wizard |
Deployment Strategy
Option 1: Parallel Deployment
- Deploy Ghostery alongside uBlock Origin initially
- Test and validate in production
- Remove uBlock Origin after confirmation
Pros: Safe, allows rollback. Cons: Temporary resource overhead.
Option 2: Direct Replacement
- Remove uBlock Origin and deploy Ghostery in one policy update
- Users get Ghostery on next browser restart
Pros: Clean transition. Cons: Brief gap in coverage during transition.
Option 3: Phased Rollout
- Migrate pilot group first
- Expand to departments progressively
- Complete organization-wide migration
Pros: Lowest risk, allows learning. Cons: Longer timeline.
Communication Template
Consider informing users about the transition:
Subject: Ad Blocker Update - Transitioning to Ghostery
Your browser's ad blocker is being updated from uBlock Origin to Ghostery. This change ensures continued protection as browser platforms evolve.
What's changing: The ad blocker icon in your browser toolbar will change from uBlock Origin to Ghostery.
What's staying the same: Your browsing experience remains protected from ads and trackers.
Action required: None. The update will happen automatically.
Need Help?
Our enterprise team can assist with your migration planning:
Need Help?
Our enterprise support team is ready to assist with your deployment.
Contact Enterprise Support