Skip to main content
When migrating to Orgo from another system (or from spreadsheets), the Data Import tool lets you bulk-create records from CSV files. Import members, local centers, roles, events, badges, products, and more — with progress tracking, validation, and error reporting. Settings → Customization → Import Data
Requires Tenant Admin permissions.

​
What you can import

The import system supports 15 data types. The platform shows a recommended import order to ensure referential integrity (e.g., local centers before members).
For each import type, you can download an example CSV template showing the expected column format. Click the download link next to each import type in the interface.

​
When to use data import

​
Preparing your CSV file

Your file must be in CSV format (comma-separated values) or TXT format. Most spreadsheet apps (Excel, Google Sheets) can export to CSV.

​
Required fields for member import

​
Common optional fields

​
Example CSV

​
The import process

1

Choose the import type

Select what you’re importing from the list (e.g., Users, Local Centers, Events). The interface shows which imports are recommended to do first and which are optional.
2

Upload the CSV file

Click Upload and select your prepared file. Accepted formats: .csv and .txt.
3

Map columns to fields

The system auto-matches common column names (email, firstName, lastName). For unrecognized columns, manually map each CSV column to the corresponding Orgo field using the dropdown selectors. The mapping configuration is saved for future imports of the same type.
4

Configure import options

Choose what to do with duplicates (skip or update), whether to send welcome emails, and other type-specific options.
5

Preview and validate

The system validates your data before importing. Review the first few rows to verify everything maps correctly. The validator flags issues like invalid emails, missing required fields, and broken references.
6

Run the import

Click Import. The system processes rows in batches with real-time progress tracking — you’ll see the percentage complete, and counts of successful, failed, and skipped rows.
7

Review results

After completion, check the summary. Download the error report for any failed rows — it shows exactly what went wrong for each row so you can fix and re-import.

​
Import status tracking

Each import goes through a workflow: The import history table shows all past imports with their status, row counts, and timestamps.

​
Import order matters

If your data has dependencies, import in this order:
1

Infrastructure first

Import Units and Local Centers — these are referenced by other records.
2

Roles and types

Import Roles (user types) — these are needed when assigning roles to members.
3

People

Import Users — now their Local Center and Role references will resolve correctly.
4

Assignments

Import User-Role assignments, Badge-User assignments, and Company-User assignments — these link existing users to existing records.
5

Activity data

Import Events, then Event Attendance. Import Products, then Product Prices and Product Payments.
If a row references a Local Center, Role, or User that doesn’t exist yet, that row will fail. The platform shows the recommended sequence in the interface — follow it to avoid dependency errors.

​
Real-world example

Scenario: A national scouting organization migrating 5,000 members from a legacy spreadsheet to Orgo.
  1. Export the spreadsheet to CSV: one file for troops (local centers), one for scout ranks (roles), one for members.
  2. Import Local Centers first: CSV with columns name, region, address. All 150 troops created in one batch.
  3. Import Roles: CSV with name, type. Creates “Scout”, “Patrol Leader”, “Scoutmaster” user types.
  4. Import Users: CSV with firstName, lastName, email, localCenter (troop name), userType (rank). The 5,000 members are processed in ~3 minutes.
  5. Review: 4,950 successful, 50 failed (duplicate emails). Download error report, fix duplicates, re-import the 50.
  6. Import Badge-User assignments: Award existing achievement badges to members based on historical records.
Total migration time: about 15 minutes for a 5,000-member organization.

​
Troubleshooting

Download the error report from the import history. Common issues: invalid email format, missing required fields, referencing Local Centers or user types that don’t exist yet. Fix the CSV and re-import just the failed rows.
Check whether you enabled “Send welcome email” during import. If not, members don’t have credentials. You can send invitation emails after the fact from the Members list, or have members use the “Forgot password” flow on the login page.
Map CSV columns to custom fields during the field mapping step. Custom fields must already exist in Orgo before import — create them in Settings → Users & Profiles → Custom Fields first.
There’s no automatic undo. For large imports, test with a small sample (10-20 rows) first to verify everything works correctly. If something goes wrong with a full import, you’ll need to manually clean up the records or contact support.
Yes. Large imports are processed in batches with progress tracking. It may take several minutes, but the system is designed for large datasets. If you encounter timeout issues, break the file into smaller batches (e.g., 5,000 rows each).