Sign in to import comparables.
Profiles your associates have made or changed. A change to an existing profile shows only what differs; approving it updates that profile for everyone.
Approved profiles everyone can import with.
A source profile remembers which column feeds which field, and which incoming values map to which codes. Mapping columns is quick; mapping values is the tedious part, and a profile means it is done once per export rather than once per file.
An Excel export or a CSV — CoStar hands you .xlsx, so drop that straight in. The first row is treated as the header. Nothing is saved until you commit at the end.
Each column in the file against the field it fills. Sample values are from the first row. Leave a column unmapped to ignore it — figures we calculate, like price per square foot, are deliberately left out so they cannot drift from their inputs.
| Column in file | Fills | Sample | Then |
|---|
Values in the file that have to land on one of our codes. Anything left unmapped is dropped rather than stored, so a stray value cannot pollute the lookups.
The export has no column for these, and they are the same for every row in it. The export date matters when a column holds an age rather than a year: CoStar measures age from the day you ran the export, not from the sale, so an old file left on today's date would date every building wrongly.
This is what will be saved, not what was in the file. Check the interpretation — a duplicate is easy to spot later, a column that landed in the wrong field is not. Untick anything you do not want.
What the file did not include. Open each in the comp ledger to finish it.