brightdata-upgrade-migration

# 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 ```typescript // BEFORE: Raw residential proxy (manual CAPTCHA handling) const oldProxy = { host: 'brd.superproxy.io', port: 22225, // Old residential port auth: { username: `brd-customer-${CID}-zone-residential_zone`, password: OLD_PASSWORD, }, }; // AFTER: Web Unlocker (automatic CAPTCHA, fingerprinting) const newProxy = { host: 'brd.superproxy.io', port: 33335, // Web Unlocker port auth: { username: `brd-customer-${CID}-zone-web_unlocker1`, password: NEW_PASSWORD, }, }; // Changes: port 22225 → 33335, zone name, password // Web Unlocker handles CAPTCHAs a...