Column mapping is a different question from where a deal lands on a board: this is about matching each column of your file, name, address, loan amount, and so on, to the right BrokerPlus field.
How Columns Are Matched
BrokerPlus tries to place every column of your file automatically, in order of confidence: an exact header match against its own field registry, a known alias for that header, then a fuzzy word-overlap guess. Anything still unplaced goes to a pass that reads the header and a sample of its values to make a best guess. A column it truly cannot place is left as "don't import" rather than forced somewhere wrong.
Opening Edit Column Mapping on the Review Screen
After a file is read, the review screen shows Edit Column Mapping. Opening it lists every column with its header, a sample value, and the field it resolved to, alongside a running count of how many columns are mapped. This is where you fix anything that landed wrong before confirming the import.
Moving a Column to the Right Field
Each row has a field picker you can search by name. Choosing a different field for a column updates the plan immediately; choosing "don't import this column" excludes it. A column you change by hand is remembered precisely as your own correction, which is what makes it reusable on the next file with the same headers.
Leaving a Column Out
Not every column in an export is worth bringing in. A field you have no use for, an internal export code, is safe to set to "don't import," whether BrokerPlus guessed wrong or simply found no match. It stays visible in the list so you can bring it back before confirming.
When Two Columns Claim One Field
Two columns can resolve to the same field, for example an export with both a legacy and a current loan amount column. The list flags these as sharing a field, but does not block the import. BrokerPlus keeps the more confident match (an exact header beats an alias, which beats a fuzzy guess, which beats the sampled guess), and for a field that can repeat, such as a second borrower's debts, files the other column as an additional entry rather than dropping it. For a field that cannot repeat, the losing column is set aside instead of overwriting a value already filled.
Saved Mappings: Reuse, Rename and Delete
Confirming an import saves its column mapping, keyed to the exact set of column headers in that file. The next file with the same headers applies the saved mapping automatically and skips the automatic matching pass entirely, so a correction you make once holds for every future export from that same source.
Every saved mapping lives under Spreadsheet Column Matching in Settings, showing its name (or the file it came from), how many columns it maps, and when it was last used. Give a mapping a name so you can tell your sources apart, expand it to see its full column list, or delete it so the next matching file starts over from BrokerPlus's own guesses. Renaming or deleting a saved mapping is limited to an admin, since it is organization-wide and changes what every member's next import does with those headers.
What to Do Next
Continue with Review and Fix an Import.