| name | brightdata-upgrade-migration |
| description | Analyze, plan, and execute Bright Data SDK upgrades with breaking change detection.
Use when upgrading Bright Data SDK versions, detecting deprecations,
or migrating to new API versions.
Trigger with phrases like "upgrade brightdata", "brightdata migration",
"brightdata breaking changes", "update brightdata SDK", "analyze brightdata version".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(git:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","scraping","data","brightdata"] |
| compatibility | Designed for Claude Code |
Bright Data Upgrade & Migration
Overview
Guide for migrating between Bright Data products, API versions, and zone configurations. Since Bright Data uses proxy protocols and REST APIs (not versioned SDKs), migrations typically involve changing zone types, proxy endpoints, or API payload formats.
Prerequisites
- Current Bright Data zone credentials
- Git for version control
- Staging environment for testing
Instructions
Step 1: Identify Migration Type
| Migration | From | To | Effort |
|---|
| Zone upgrade | Web Unlocker v1 | Web Unlocker v2 | Low |
| Product switch | Residential Proxy | Web Unlocker | Medium |
| Browser migration | Puppeteer direct | Scraping Browser | Medium |
| API migration | Datasets v2 | Datasets v3 | Medium |
| Full platform | Competitor | Bright Data | High |
Step 2: Migrate from Direct Proxies to Web Unlocker
const oldProxy = {
host: 'brd.superproxy.io',
port: 22225,
auth: {
username: `brd-customer-${CID}-zone-residential_zone`,
password: OLD_PASSWORD,
},
};
const newProxy = {
host: 'brd.superproxy.io',
port: 33335,
auth: {
username: `brd-customer--zone-web_unlocker1`,
: ,
},
};