Open Data In and Out → Upload a file to start the wizard. You need the importer:execute:import permission; without it the page names the permission to ask your administrator for. The page is titled Import Data, and the wizard’s six stages run down its left-hand side: Select file, What to import, Map columns, Pre-flight check, Review & submit and Job status. You can click back to a completed stage until you start the import.
Two controls sit above the wizard: Bank statement, which opens the bank statement importer, and the Create lookup values if they don’t exist switch (see stage 4).
1. Select file
Click the file area or drag in a prepared CSV, then click Next. This reads its headers; the file is uploaded when you submit the job.
2. What to import
Select one or more entity cards and click Continue. One selected type gives a single-type import. Several types create a pipeline in the displayed Processing order; there is no separate Single/Pipeline mode selector or manual Add step button.
For related records, read Run a pipeline import before continuing.
3. Map columns
The table lists destination Field and Source. Review the suggested file column for each field; matching headers are suggestions, not confirmation that values are correct.
- Pick a source column, choose Static value to assign a value to every row, or leave the field Not mapped.
- Use Combine columns… to join several columns with a chosen delimiter.
- Use Value mapping to translate source values. An empty default output passes an unmatched value through unchanged.
- Use Default if empty to replace blank or whitespace-only incoming values. It does not override non-empty values and is unavailable for consent fields.
- Map source identifiers under External Keys, supplying both the source platform and its ID column.
- For consent channels, map the consent value and select the purposes that consent covers. Do not infer consent merely because a contact has an email address.
Mapped empty standard fields can clear values on existing records. Unmapped fields are left alone. Custom fields have a separate Clear when blank setting; leave it off to preserve an existing custom-field value when the incoming cell is blank. Custom fields are available for contacts, organisations and resources when configured for your beehive.
4. Pre-flight check
Wait while the wizard reads every row. Confirm the file’s date format if date columns are mapped. Fix missing required mappings before continuing; the wizard blocks these. Value problems identify affected rows but can be advisory, so continuing with warnings can still produce failed rows. Pre-flight checking does not write records and cannot prove every referenced record exists.
If lookup values need creating during an initial migration, deliberately turn on Create lookup values if they don’t exist at the top of the page. With it on, unrecognised values for lookup fields (fundraising activities, touchpoint types and similar) are created rather than failing the row, and Review & submit shows the mode as Initial import. Check the values first: a misspelling becomes a new setting.
5. Review & submit
Check the file, selected entities, mapping counts, processing order and date format. To reuse the setup, enable Save this mapping for next time and enter a name.
Click Start Import. The wizard uploads the file and creates the job. It has no cancel or rollback button; leaving the page or clicking Start new import does not undo records already written.
6. Job status
Watch the status and processed/error counts. A pipeline also shows per-entity progress. If rows failed, click Download error report.
Every job is also listed under Recent imports below the wizard, with its file, entity type, status, created time and row count. Click View to open Import job details, including the job ID and, where available, the error report. Use Load more for older jobs. Open representative imported records to check values and links before using the same setup for a larger file.
See Job statuses and errors for reports and recovery, and Save and reuse a column mapping.