Chrome has no built-in "edit site URL" function in its password manager, but you can still update saved logins for a rebranded domain in bulk: export all passwords to a CSV file, change the url values for the affected entries in any text editor, and import the file back. Chrome skips entries it considers duplicates, so untouched rows cause no conflict, and the corrected credentials begin autofilling immediately.
Why autofill breaks after a domain change
Chrome keys each saved credential to the exact origin (scheme plus host) where it was entered. When a service migrates from, say, oldbrand.com to newbrand.com, the login page at the new host has a different origin, so Chrome treats it as an entirely unknown site. The saved passwords still exist — they are simply associated with the old address and will never surface on the new one.
Individual entries can be deleted from the password manager, but the edit dialog only allows changing the username and password, not the site they belong to. There is no per-entry or bulk "relink" option in the UI, which is why the export-and-import route is the practical solution.
Step 1: Export your passwords to CSV
- Open Chrome's settings and navigate to the password manager (search for "passwords" in the settings search box, or visit
chrome://settings/passwords). - Use the overflow menu next to "Saved Passwords" and choose Export passwords.
- Confirm the export; Chrome asks for your OS-level login to authorize it, then downloads a plain CSV file.
Security warning: this file contains every username and password in cleartext. Do it on a trusted machine, do not email or cloud-sync the file, and delete it as soon as the migration is finished.
Step 2: Edit the affected rows
Open the CSV in a text editor or spreadsheet application. The format is a simple header followed by one row per credential:
name,url,username,password,note
www.example.com,https://www.example.com/login,jane,secret123,
Only the url column needs to change for a domain migration. Replace the old domain with the new one in each affected row — include the scheme (https://) and any path Chrome originally stored, since Chrome matches against what is in that field. For example, https://www.oldbrand.com/login becomes https://www.newbrand.com/login.
If you edit in a spreadsheet instead of a plain-text editor, be careful to save back as CSV with the same column order, and watch out for quoting changes; a plain editor is usually safer for this kind of find-and-replace.
Step 3: Import the corrected file
- Back in the password manager, use the same overflow menu and choose Import passwords.
- Select your edited CSV file.
- Chrome ingests the entries and creates new credentials for the new-domain rows. Existing rows that duplicate what is already stored are skipped, so the rows you did not modify cause no errors or unwanted duplicates.
Once imported, visit the new site and verify that Chrome now offers the saved username and password. If you no longer want the old-domain entries cluttering the list, delete them individually from the password manager — it is easier to do this afterwards, when you can confirm the new entries work.
If the Import option is missing
On some Chrome versions and platforms the import command is hidden behind a flag. Type chrome://flags in the address bar, search for "Password import", enable the flag, and relaunch the browser. The Import option then appears in the password manager's menu. If the flag is unavailable on your version, an alternative is to add the new-domain entries manually by logging in once at the new site and letting Chrome save the credentials — but for a handful of sites, manual re-entry may genuinely be less work than the CSV round-trip.
Prevention and good practice
- When a provider announces a domain migration, ask whether they set up an automatic redirect; even so, Chrome will not remap stored credentials for you.
- Consider a dedicated third-party password manager, many of which support editing a site URL directly and sometimes offer URL-matching rules that tolerate domain changes better.
- Periodically review your password list so you know which services are tied to which domains — this makes the next migration a five-minute task.
- Always verify you can log in at the new domain manually once before trusting the migrated autofill data.
Frequently Asked Questions
Can I edit a saved password's site URL directly in Chrome?
No. The edit dialog in Chrome's password manager only allows changing the username and password fields. Changing the associated site requires the export/edit/import workaround or deleting and re-creating the entry.
Will importing the CSV create duplicates of every password?
No. Chrome skips rows that duplicate existing entries, so only rows where you changed the URL (or added new data) result in new stored credentials. Unmodified rows are effectively ignored.
Is exporting passwords to CSV safe?
The file is unencrypted, so it is only as safe as where you keep it. Export on a trusted device, edit locally, import, and then securely delete the file. Avoid leaving it in Downloads or syncing it anywhere.
Do I need to delete the old-domain entries?
Not immediately. Chrome will simply stop showing them on the new site. It is cleaner to remove them once you have confirmed the new credentials work, but leaving them causes no functional harm.
Does this work in other Chromium-based browsers?
Browsers such as Edge and Brave offer similar password export/import features, though the menu locations differ. The CSV editing approach is the same; just check the column headers in the file that browser produces.
What if the new site still doesn't autofill after import?
Double-check that the imported URL matches the actual login page exactly, including https:// and any path. Log in manually once and confirm Chrome offers to save the password — if it saves a slightly different URL, that is the one you need in your CSV.