Purpose: Choose the right import workflow and run imports safely—especially when updating existing records or importing data with dependencies.
Related: Importing data into Administrate
For how the import system works (templates, field types, processing, and errors), see: Import Data: System Behavior, Templates, and Field Types.
When to use imports
- Bulk creation of records during onboarding/migration.
- Bulk updates when you have stable identifiers and verified matching behavior.
- Controlled correction of known issues (targeted subset imports).
Recommended workflow (safe and repeatable)
- Plan: identify what you’re creating vs updating, and confirm identifiers.
- Prepare: build a clean CSV with consistent formatting.
- Pilot: run a small subset import first.
- Scale: proceed in batches.
- Verify: reconcile outcomes after each batch.
Key references:
Workflow patterns
A) Creating new records (low risk when identifiers are clear)
- Use consistent identifiers where applicable.
- Watch for lookup/reference fields that require existing values.
- Verify counts and spot-check key fields after import.
B) Updating existing records (higher risk)
- Confirm identifier fields and matching behavior before you run.
- Run a pilot subset and confirm that rows update existing records (not create new ones).
- Proceed in batches and verify after each batch.
C) Corrective imports (after failures or partial success)
- Fix only failed rows and re-import the subset (avoid re-running full CSV).
- Use verification and troubleshooting references to close the loop.