How should I handle Excel formula columns before moving data into Busabase?

I would sort the Excel columns into inputs, frozen results, and live calculations before moving the rows.

• Keep the inputs that explain each result, such as quantity, unit price, discount, and currency.
• If an amount represents a past approved invoice or a period-end balance, copy its current value into an ordinary Number field, with an “as of” date or source note. That is a snapshot: later edits to the inputs should not rewrite history.
• If an amount should change whenever its inputs change, create a Busabase Formula field from those inputs. For example, a working amount can be calculated from quantity and unit price; an approved invoice amount remains a separate snapshot. Recreate and test the rule in Busabase rather than assuming the Excel expression transfers as-is.

One important detail about the current Base Import records dialog: you paste rows copied from a spreadsheet and review how columns map to fields. It imports cell values, not Excel's formula definitions; computed Formula fields are skipped during paste. Put snapshot results in Number fields and leave live Formula fields to Busabase. If a calculation refers to other sheets, other records, or an external workbook, map those dependencies first and test that particular calculation separately.

I would try 5–10 representative rows before the full import: include blanks, discounts, rounding, and one cross-sheet formula. Compare the snapshot numbers with Excel, then change an input on a test record and confirm that only the intended live calculation updates. Keep the original workbook until those checks pass. See Bases and Field Types for the underlying structure. Are your amounts mostly within one row, or do they depend on totals from other sheets?