Importing and Exporting Data

Rivolq brings structured records in from CSV and Excel files and sends operational data out through page exports, reports, scheduled exports, and APIs.

Importing

Open Imports and drop a file. Rivolq reads the record types and column mapping, then presents only the questions it cannot answer safely. Those questions can cover facility assignment, duplicates, uncertain columns, fixable values, and rows that need attention.

The main workspace is one page. Detailed mapping, row, and duplicate views remain available as optional investigation tools. Read the final write summary and press Add to Rivolq only when it matches your intent. Nothing is written before that action.

The completed batch stays available so you can find what it created, reconcile errors, and retain the source as evidence. For a walkthrough, see Import assets and facility data and Bulk import review and commit.

Deduplication

Stable identifiers such as asset tags and serial numbers produce the strongest matches. Similar names can still be presented for review. Choose update only when the imported row is the same real-world record. Choose create for a genuinely separate record. Skip rows that should not enter the workspace.

Exporting

• Per-page export: export the filtered records offered by a list page.
• Reports: generate the formats available to your plan from the reporting surfaces.
• Scheduled exports: on eligible plans, schedule CSV, JSON, or XLSX delivery to configured email, webhook, S3, or SFTP destinations. See Scheduled exports.
• API: Intelligence and higher plans can use developer API access for programmatic integrations.

Safe operating pattern

• Keep the source file.
• Read the import summary before writing.
• Investigate surprising counts instead of adding records to see what happens.
• Verify a sample after completion.
• Use scheduled exports or APIs for repeatable synchronization rather than repeated manual imports.