Custom fields — capture what we don't model

Every shop tracks something STrOp didn't have a box for — a customer P.O. number the GC wants on every invoice, an internal job classification your accounting lives by, the vendor code from your old system. Until now that overflow lived in a spreadsheet, and the spreadsheet quietly became the system of record.

Settings → Custom Fields ends that. An admin defines a field once — text, number, date, a single pick, or a multi-pick with your own option list — on projects, companies, or contacts. From then on it's just there: in the create form, on the edit page, on the record's detail view, validated like everything else. Mark a field required and new records can't skip it.

Fields you stop using archive instead of deleting — the captured values stay put, they just stop appearing on forms — so an old field's history survives a process change. And when you migrate off Foundation or Sage with a column we've never heard of, it now has a first-class place to land.