Why import?
When you switch to tikento from another service, you don't want to lose your history: events, participants, tickets, payments, promo codes. Import lets you transfer all of this in minutes.
tikento follows the no vendor lock-in principle in both directions: we offer free data export, and entry should be just as easy.
Supported sources
| Source | Import methods | Status |
|---|---|---|
| Timepad | API (developer token) + CSV/XLSX | Available |
| Qtickets | — | Planned |
| Eventbrite | — | Planned |
| Nethouse.Events | — | Planned |
| Other | CSV/XLSX (universal) | Planned |
Two import methods
Via API (recommended)
Automatic data loading through the old service's API. You enter an access token — tikento loads all events, participants, tickets, and payments automatically.
Advantages: maximum data, automatic field mapping, no file downloads needed.
Via file (CSV / XLSX)
You download an export from the old service's dashboard and upload it to tikento.
Advantages: no API token needed, works even if the service's API is unavailable, suitable for large databases (no rate limits).
What transfers
| Data | API | File |
|---|---|---|
| Events (name, dates, location, type) | yes | yes |
| Ticket types and prices | yes | partial |
| Participants (name, email, phone) | yes | yes |
| Form responses | yes | yes (by columns) |
| Orders | yes | yes |
| Payments (read-only archive) | yes | yes |
| Promo codes | yes | partial |
| Check-in (attendance marks) | yes | yes |
| Event cover image | yes | no |
What doesn't transfer
- Payment gateway connection from the old service (set up payments in tikento separately)
- Venue seating maps
- Team roles and settings
- Printed ticket barcodes (tikento generates its own QR codes)
- Internal reports from the old service
How to start
- Go to Settings → Data Import.
- Click Start import.
- Choose the source and method (API or file).
- Follow the wizard steps.
Detailed instructions for each source are in the corresponding article.
Security
- The old service's API token is not stored after import completion.
- Import does not send emails to participants. Communication with the imported database requires your explicit action.
- All data is protected by encryption and tenant isolation.
- Before importing, you confirm the right to process participants' personal data.
- Uploaded files are validated for security (size, format, zip bomb protection).
Re-import
Re-running import on the same data is safe: the system checks each record and skips already imported ones. New records (e.g., those that appeared after the first import) will be added. No duplicates are created.