Skip to main content
CSV upload is the universal way to bring data into Novaplan. Any domain (people, GL, ARR actuals, or pipeline) can be loaded from a spreadsheet, so you can start planning on real numbers before a live connector is in place, or backfill a one-off feed at any time.

​
Upload a file

1

Start the upload

In Admin -> Data, choose CSV upload and select the domain the file belongs to.
2

Map your headers

Match each column header to a canonical field. Nova can suggest a mapping from your headers, which you review and adjust before saving.
3

Validate

The file lands as a lossless raw record, then curation validates each row. Rows that fail are flagged individually with a reason; good rows curate.
4

Confirm

Check Pipelines to confirm the rows landed and to read any per-row errors.

​
File format and headers

  • Use a header row; column order does not matter because you map headers to fields.
  • One row per record (one person, one GL posting, one ARR event, one opportunity).
  • Use plain text for identifiers and numeric values for amounts (avoid currency symbols and thousands separators inside numeric cells where possible).

​
Columns by domain

DomainColumns to provide (map to canonical fields)
PeopleEmployee ID, name, job title, department, site, start date, end date, status, comp
GLAccount, department, entity / vendor, period (month), amount, memo
ARR actualsAccount, event month, ARR delta, movement component, customer count delta
PipelineAccount, stage, amount, expected close, owner, segment
Dates must be real dates that parse cleanly. A month field is expected as a full date (the first of the month), not a bare year-month string, so that it casts and normalizes correctly during curation.

​
Common questions

No. Validation is per row. The good rows curate and the bad rows are flagged with a reason, so you fix and re-upload only what failed.
Yes. Curation is idempotent: re-uploading the same batch replaces its prior rows rather than duplicating them.

​
Troubleshooting

  • Rows fail with a date error: the date did not parse. Provide a full date (for a month field, the first of the month) and re-upload.
  • A value is not rolling up: the raw value is unmapped. Add the mapping in Dimensions or GL Mapping, then re-run curation.
  • A required field is missing: the file is missing a column the domain requires, or it is not mapped. Add or remap it and re-upload.
  • Amounts import as text: keep numeric cells unformatted so amounts curate as numbers.