How to handle Google’s 3,000-password import limit
Google allows 3,000 passwords per import file and up to 10,000 stored passwords in an account. The safest response is deliberate batching—not repeatedly retrying one oversized plaintext file.
Count before export
Run a local preflight and note the total number of valid rows. Remove obvious exact duplicates and entries you no longer need. This reduces the number of files without weakening the review. PortaPass shows selected and total counts and blocks oversized Google output.
Create bounded batches
Select no more than 3,000 entries for each Chrome-compatible CSV. Use stable, non-overlapping batches and import one at a time. Keep a password-free note of the batch names and counts if you need to track progress; never create a checklist containing the credentials themselves.
Verify each result
After each import, read Google’s result and sample several entries from that batch. Stop if conflicts or unexpected losses appear. Fix the source mapping before continuing so the same problem is not repeated across every file.
Delete completed files
Delete each batch once its import is verified. Do not keep all generated files until the end without a reason; that multiplies the exposure window. When the migration is complete, verify the account total and remove the original source export too.