Agencies migrate profiles between operators, workspaces, or anti-detect vendors. Cookie-only import without matching fingerprint + proxy often triggers instant logout or account review — the session was bound to the old browser identity.
Transfer methods
| Method | Preserves | Risk |
|---|---|---|
| Full profile export (MLX native) | Cookies, storage, fingerprint preset | Lowest if same MLX version |
| Cookie JSON import only | Session tokens | High if fingerprint/geo differs |
| Clone profile in workspace | Everything except history | Medium — update proxy if client changes |
| Fresh profile + manual login | Clean identity | Safest for burned accounts |
Safe handoff checklist
- Export from source profile while stopped (not running)
- Document proxy endpoint — import with same sticky IP or re-login
- Match OS preset and timezone on destination profile
- Import → single manual navigation before automation
- Revoke source operator access — agency offboarding
Never do this
- Import same cookie file into two running profiles simultaneously
- Transfer cookies from vanilla Chrome into MLX without fingerprint alignment
- Swap proxy country during first post-import session
- Mix mobile app cookies with desktop Multilogin profile
Playwright cookie inject (advanced)
# After CDP attach — only when fingerprint already matches session origin
await context.add_cookies([
{"name": "session", "value": "...", "domain": ".example.com", "path": "/"}
])
await page.goto("https://example.com/dashboard")
Prefer native MLX storage over manual inject when possible.
Related
Disclosure: MLX-MMO affiliated with Multilogin.