Import data

Steps

1. Choose the import kind. Templates — the fields your columns map to — exist for six kinds:
   • The investor register.
   • Three kinds that migrate a fund from another system: its commitment register, its capital activity history, and its opening balances. Each belongs to the fund being migrated, which you choose when you upload, and is accepted only while that fund’s migration is open — see Migrate an existing fund.
   • The trial balance and the chart of accounts. These can be uploaded, mapped, and validated in staging, but promoting them is not yet available.
2. Upload. A CSV file, with encoding, delimiter, and header detected automatically. Excel workbooks import separately — see below.
3. Map columns. Match your file’s columns to NAVdryx’s fields, or reuse a saved mapping from a previous import.
4. Validate in staging. Nothing lands in production data yet — the staging area holds the draft import while you review it. A fund-migration import is also checked against its fund: every party must match exactly one existing record, every date must fall inside the migration window, every amount must be in the fund’s currency, and the calculation engine checks that the money adds up.
5. Read the error report. Row-level issues are called out explicitly rather than failing the whole import silently.
6. Promote to production. An explicit, separate action — the import cannot become live data by accident. Available for investor register imports and the three fund-migration kinds.

A fund accountant, fund administrator, or fund controller uploads, maps, and validates an import. Promoting it takes a fund controller who did none of those for that import: whoever uploaded the file, saved its column mapping, or ran its validation cannot promote it, so every import is checked by a second person before it becomes live data.

Excel specifics

An Excel workbook (.xlsx or .xlsm) imports as a workpaper. Import preserves sheet structure and detects formulas, external links, hidden sheets, and macros. Formula support has an explicit, stated scope — arithmetic, statistical functions, lookup functions (VLOOKUP, INDEX/MATCH, XLOOKUP), conditional functions, and date functions. A formula outside that scope converts to a static value with a flag, so you know it happened. External links convert to a static value with a flag the same way. Macros are stripped on import and flagged. An imported workbook is held in staging for review; it can’t be promoted into production data.

If something looks wrong

Because production data is never touched until you explicitly promote a staged import, a bad mapping or a dirty source file costs you a re-upload, not a cleanup job against live records. Fix the source file or the mapping and re-run validation before promoting again. Capital history that a fund migration has already promoted is corrected differently: void that import’s history on the fund’s migration page while the migration is open, then import the corrected file.