Import & Export#

Novaza Office includes a built-in importer and exporter for moving record data in and out of any module. This is useful for onboarding existing data, producing snapshots for offline analysis, and exchanging data between namespaces.

Supported Formats#

• CSV — Comma-separated values, with a header row for field mapping
• JSON — Line-delimited or array-based JSON, preserving nested structures and typed values

CSV is typically used for data produced by spreadsheets and legacy systems. JSON is preferred when field types are complex (multi-value fields, record references, JSON blobs).

Importing Records#

1. Open the target module and click Import.
2. Upload a CSV or JSON file (up to 50 MB per upload).
3. Map each source column to a module field. Unmapped columns are ignored.
4. Choose an import mode:
   • Create only — skip rows whose primary key already exists
   • Update only — update existing records, skip new ones
   • Upsert — create new or update existing based on a chosen key field
5. Preview the first ten rows, then click Start Import.

The importer runs asynchronously and emits a completion notification. A detailed result log reports success count, failure count, and per-row errors (for example, invalid option values or missing required fields).

Exporting Records#

From any module’s record list page, click Export. Choose the output format (CSV or JSON), the fields to include, and an optional filter to narrow the export (for example, only records created in the last 30 days).

Exports are generated server-side and made available as a download link once ready. Large exports (over 100k rows) are delivered via email notification with a time-limited download URL.

Scheduled Exports#

Recurring exports can be configured as a scheduled workflow (see Workflows). A scheduled export writes the file to an attached storage location or attaches it to a notification email sent to configured recipients.

Permissions#

Import and export respect module-level and field-level permissions. Users can only import into modules where they hold Create or Update rights, and exported files include only fields the exporting user is allowed to read.