Import overview
Understand the CSV import flow, supported destination tables, run states, and safe operating boundaries.
Import turns one CSV file into records in a selected Infra One destination. Before the run starts, the wizard brings the file metadata and column mapping together for review. Afterward, the detail page retains the filename, target, status, processing counts, and row errors without treating the import as an all-or-nothing transaction.
How the wizard works
Every import follows Select database table → Upload CSV data → Map columns → Review and import. Enrich data and Conflict strategy appear between mapping and review only when the selected destination supports them. Entity currently uses both optional steps; the other current destinations use the four required steps.
Selecting Start beside a destination creates a Pending Import record and opens the upload step. You can save the configured import as a draft or start it from the review step. When processing begins, the record becomes Processing. A finished run becomes Completed, even when individual rows failed. A run-level failure becomes Failed. The background worker can make up to three total attempts, so Failed can appear before automatic attempts are exhausted.
Supported destinations
The current destination picker contains eight tables:
- Account
- Classification
- Contact relationship
- Entity
- Entry
- Subledger account
- Subledger group
- Subledger structure
The fields and required mappings depend on the selected destination. Review the destination and mapping on the final step before starting the run.
What completion means
Completed means the processor finished the run. It does not mean every CSV row created a new record. The result can include created rows, updates to matched records, matched rows that needed no change, skipped rows, and failed rows. Use Processed records, Failed records, Updated records, Skipped records, Success rate, and Error details together when reviewing the outcome.
Deleting an Import record removes its history. It is not a rollback: entries already created in the destination are not deleted.
Current access boundary
Use Import only with an organization and destination your administrator has approved. Authentication and the normal workflow are documented here; permission and destination-access rules remain under verification. This documentation does not promise that membership alone authorizes every Import record or destination.