Switch from pretix
Move your pretix events and products into TixFin as drafts
TixFin reads two of pretix's own exports, converts them in your browser and checks them like any other import. Your events arrive as drafts with their ticket types.
Where: Events & tickets → Events → New event → Import from a file → pretix. Who can do this: Create events, and Create ticket types when you upload product data.
What moves, and what does not
| From pretix | Into TixFin |
|---|---|
| Short form | ref — each ticket type names it |
| Event name | name |
| Event start and end time, time zone | startsAt, endsAt with the event's offset, timezone |
| Location | location |
| Event currency | each ticket type's currency |
| Product name, and variation | ticket type name, as Product – Variation |
| Default price | price |
Only active products and variations are read. Quotas are not part of pretix's product export, so every ticket type arrives with no stock limit: set its stock before you publish. Orders, attendees, customers and any buyer data stay at pretix; never upload an order list. Dates of an event series, vouchers, questions and seating plans are not read.
Export from pretix
<short form>_products.csv: it tells TixFin which event the products belong to.Import into TixFin
Before you publish
- Set the stock of each ticket type; it arrives unlimited.
- Add-on products, such as merchandise or parking, arrive as ticket types too. Delete their rows in the converted file if you do not sell them as tickets.
- A free price input product arrives at its default price as a fixed price.
- An event without an end time is refused:
endsAtis required. Add it in the converted file. - Text starting with
=,+,-or@is refused. pretix's export marks such text with a leading'; TixFin removes the mark, so the check sees the text as you wrote it. Reword its first character in the converted file.
Importing the same files again saves nothing and says so. See Import events from another system for the limits and the TixFin templates.