Skip to content
Fieravents
Menu

Migrating

Your people, catalogue and booth history move across.

Attendee records, ticket types and prices, exhibitor contacts, booth history and last year’s floor plan. The booth history is what your first priority-points selection runs on, so it comes over first.

Moves cleanly

  • People. Names, addresses, organisations, and the history of what they attended, resolved to one identity per person rather than one per import file.
  • Your catalogue. Ticket types, prices, tiers and add-ons become products and price rows.
  • The exhibitor list. Companies, contacts, booth history and what they paid — which is what priority-points selection runs on.
  • The floor plan. Imported as a calibrated underlay and drawn over, rather than retraced from a PDF by eye.
  • Last year’s agenda. As the starting point for this year’s, which is how programs are actually built.

How the switch runs

  • We import, you review. Your data lands in your own database and you check it against the old system before anything goes public.
  • Between cycles, not mid-sale. The switch happens while registration is closed, so no attendee is ever halfway through a form in two systems at once.
  • Badges reissue free, and instantly. Every attendee gets a credential that resolves against your live roster, at no cost and with no reprint run.
  • A small event first. Run one live before the flagship. There is no per-event fee, so the rehearsal is free.

The one to time carefully

Start with your smallest event, then take the flagship.

Run a chapter meeting or a workshop series first. There is no per-event fee, so the pilot costs you nothing. By the time your flagship arrives, your team has already worked a live door on the system.

It is also the fastest evaluation available. A small live event tells you more in a week than a demo tells you in a month.

And leaving

Take your data out whenever you want.

Your data sits in a database that holds your tenancy and nothing else, and every action the interface performs is an API endpoint you also have. Take the database whole, or pull it through the API.

We would rather be kept than be hard to leave.

What is the smallest event you run?

That is usually the right one to run first, and often the one currently on a spreadsheet.

hello@fieravents.com