Multiple username/passwords stored under a single entry

@MaddTech83 It seems you did the wrong approach in the first place when you decided to add multiple login credentials to one 1Password item.
I suggest you take the time and redesign your setup to best practice and what 1Password supports best.
You seem to have sites, and you seem to have developers who login to these sites. Every developer has its own login. You seem to have 7 developers and about 2000/7 = 285 sites.

How about this setup:
- create one shared vault for every developer
- into one developer vault, put the 285 entries with his login. These entries have only 1 username+password.
- tag the entries the following way: site/developer.

Since you want shared access, give every developer access to every vault. However, in the app, as well as the browser extension, you can configure which vault is currently visible and items from it displayed. If one developer is using only his credentials, he can activate his vault only and ignore the other vaults. This way he only sees the items meant for him, and he is offered only his logins when he is about to login.

How to get to all these entries:
Since you say "developers", they might perhaps have something to do with IT. If this is the case, let one of your developers do this:
- export the vault that currently contains the 285 entries that contain all username+password pairs to *.1pux
- extract the export (it's a zip file renamed to 1pux). It contains a json file you can manipulate with json tools and scripting.
- create 7 copies of that json, one for every developer. For every distinct json, remove all but 1 of the username+password pairs, so you get 7 json files with the logins for one developer only.
- recreate 7 *.1pux files from the 7 json files
- import the 7 *.1pux files in 1Password. They will end up as 7 different vaults. You will never overwrite existing entries, so there is no danger to your existing entries
- add the tags I meant to the entries. Either now or while creating the json files with the conversion script you created.

I recommend python for manipulating json data (if you have som python developer), and the jq tool should also be able to do this, although this is not very common knowledge.

A more simple approach would be to export as *.csv, not as *.1pux, however with csv you have much less freedom which fields can be used. I don't know if all of your 7 different custom login entries will all show up.