Start a CSV import

This guide verifies the file and mapping on Review and import, starts one CSV import, and leaves you on its progress page with the filename, target, status, counts, and errors visible.

Before you begin

You need:

• access to https://import.infra.one/your-organization-slug;
• an approved organization and destination for the data;
• CSV only: one .csv file no larger than 50 MB (50,000,000 bytes);
• a header row and values that can be mapped to the destination’s required fields;
• a plan for validating created or updated destination records after the run.

Permission and destination-access rules remain under verification. Use only the organization and destination that your administrator approved, and do not test access with another organization’s URL or Import identifier.

Create and start the import

1. Open https://import.infra.one/your-organization-slug and select Import.
2. On Select database table, select Start beside the intended destination. The current picker includes Account, Classification, Contact relationship, Entity, Entry, Subledger account, Subledger group, and Subledger structure.
3. On Upload CSV data, add one .csv file. If the file is rejected, remove it before continuing.
4. On Map columns, map the CSV headers needed for the import and ensure every required destination field has a mapping. Unused CSV columns can remain unmapped. Resolve every required-field warning before selecting Next.
5. If Enrich data appears, choose the source column, value type, and enrichment behavior. This optional step appears only for a destination that supports it.
6. If Conflict strategy appears, choose how the import should handle matching destination records. This optional step also depends on the destination.
7. On Review and import, enter an Import name and compare the destination, file size, mapped columns, and final mapping with the intended setup.
8. Select Save as draft if the run is not ready. Otherwise, select Start import.
9. If a preview appears, review new categories and validation errors. Fix blocked rows in the CSV and re-upload them; select Confirm and import only when the preview is ready.
10. Confirm Import started successfully, then select View progress.

Success check

The Import detail page shows the correct filename, destination table, and uploader. After you start the run, it can remain Pending while queued; it becomes Processing when the worker begins. After it finishes, verify the final status, processed and failed counts, success rate, and any Error details. A Completed run can still contain failed rows, so validate the destination records before treating the work as finished.

Troubleshooting

• The file is rejected and Next remains unavailable. Remove the rejected item. Upload one .csv file within the 50,000,000-byte limit.
• A required mapping is missing. Return to Map columns and map every required destination field.
• The preview lists validation errors. Correct those rows in the source CSV, upload the corrected file, and review the mapping again.
• Could not preview the import. Keep the draft. Use Previous to verify the target, context, file, and mapping; preserve the organization, Import name, time, and visible message. Do not infer or publish the logged reason. Contact support if the generic message persists.
• Could not start the import. Keep the draft. Use Previous to verify the target, context, file, mapping, and name. Do not repeatedly start it; preserve the visible details and contact support if the generic message persists.
• The run becomes Failed. There is no generic user-facing retry for the same failed record, but the background worker can make up to three total attempts. Preserve the visible error and contact support to confirm that no background attempt remains. Reconcile destination records and any other persisted changes across attempts before correcting the input or setup and starting a replacement import.

Related pages

• Import overview
• Run, review, and clean up imports
• Troubleshoot Import