Data migration considerations
Ninox’s import tool reads CSV and Excel files and walks you through mapping spreadsheet columns to fields in a Ninox table, including basic type conversion for text, numbers, and dates. It does not automatically infer relationships between tables during import — linked-record fields, such as connecting an Orders table to a Customers table, generally need to be set up as relation fields and re-mapped after the raw records land.
Practical Details
Because NinoxScript formulas, triggers, and layouts live in the database design rather than in the imported data, migrating from another system such as Airtable, Excel, or an old CRM only brings over the raw records — any calculated fields, validation rules, or automation relied on in the source system have to be rebuilt natively in Ninox. Large imports of tens of thousands of rows are best done in batches so errors are easier to isolate and fix.
Actionable Considerations
- Prepare a mapping of spreadsheet columns to Ninox field types before importing, flagging which columns should become relation fields
- Import a small batch first in a test database to confirm types, date formats, and relations resolve correctly
- Rebuild formulas, triggers, and permission rules natively in Ninox rather than assuming they carry over from the source system