Moving Off Momentus, Ungerboeck or Priava Without Stopping Trading

Replacing a venue management system is not like replacing most software. A stadium cannot close its calendar for a fortnight while the new one goes in. Holds are live, events are being detailed, invoices are going out, and the building needs to know what is on next weekend.

This is the plan we recommend for Australian stadiums and large venues moving off Momentus, including the products that used to be Ungerboeck, VenueOps and Priava. It assumes you have already decided to move. If you have not, start with signs you have outgrown Momentus and the alternatives to Momentus. Facts about Momentus below were checked against its own site and help centre on 2 October 2026.

A quick note on names. Ungerboeck rebranded as Momentus in early 2023. EventBooking, maker of VenueOps, merged with Ungerboeck in May 2021, and Priava was acquired by Ungerboeck, now Momentus, in November 2021. Momentus Enterprise is the former Ungerboeck product and Momentus Elite is the former VenueOps, and the old Ungerboeck, Priava and EventBooking websites now redirect to Momentus. Whichever of them your venue runs, the plan below applies.

Momentus is a capable suite, and moving off it is a real project. Momentus says its Elite implementations for small and mid-sized venues typically run one to three months, and Enterprise implementations run longer, depending on data migration complexity, integration scope and customer readiness. Leaving takes a similar order of effort, so plan for it.

1. Start with the contract

Before anyone looks at data, find the agreement. Momentus says its contracts are typically multi-year with annual billing, but the terms that matter are the ones in yours, so read them rather than assume.

Write down:

1. The end date of the current term.
2. Whether it renews automatically, and for how long.
3. The notice period, and how notice must be given.
4. What the agreement says about your data at the end: export, format, assistance, any fees, and when it is deleted.
5. Whether you can keep read-only access after the term ends.

Then work backwards. The notice date is your real deadline, and the migration has to fit in front of it with room for a venue or two to slip. If anything about data at exit is unclear, ask the vendor in writing now, while you are still a customer in good standing.

If you are a NSW government agency, the ICT Services Scheme is mandatory when you buy ICT services, so check the procurement route early. It shapes the timeline as much as the product does.

2. Inventory what the system actually does

Licensed modules and used modules are rarely the same list. Before you choose anything, document what your current system does day to day:

• Modules in use, and which venues use them.
• Integrations: finance, CRM, website feeds, digital signage, e-signature, ticketing, building systems.
• Reports people depend on: who runs them, how often, and who reads them. A board pack or a monthly utilisation report is a requirement, even if nobody calls it one.
• Custom fields, statuses and templates, including proposals, contracts and event orders.
• Users and roles, by venue.

The quickest way to find the hidden ones is to ask each team what would stop them working on Monday if the system disappeared. Products in this space are built to be customised. Momentus’s own Priava material advertises more than 40 report templates and customisable event statuses, so expect your setup to differ from the defaults.

3. Get your data out

Momentus documents several ways to reach your data:

• Its integration architecture is Momentus Connect: open APIs, OData endpoints, webhooks and SSO.
• The Momentus Enterprise API has SDKs and examples published on GitHub, with example repositories for recent releases.
• The Momentus Elite Open API can read or write most major record types, from accounts and contacts to events, booked spaces and functions, and Momentus says documentation is available to all users of the API. Elite reports in Insights, where it is enabled, can also be exported to file.
• For Priava, Momentus lists API & Integrations as an add-on module, so check whether yours includes it.

What we could not verify publicly is what a complete end-of-contract export contains: whether it includes attachments, history, audit records and financial detail, in what format, and at what cost. Ask in writing, and ask for the schema documentation with it.

Then do a trial extract early, not in the last month. Count bookings, accounts and events per venue in the old system and in the extract, and make sure the numbers agree. A migration you cannot reconcile is a migration you cannot sign off.

4. Map spaces, holds and statuses

This is where most of the thinking goes, because systems model venues differently.

Spaces. Momentus Elite uses rooms and combo rooms, where a combo room can be broken down into smaller spaces. Your new system may model a deeper hierarchy: a stadium containing concourses containing rooms that combine and subdivide. Build a mapping table with every old space, its new equivalent, its parent and what it conflicts with. Then test it with real clashes from last season, not invented ones.

Holds. In Elite an event can be Inquiry, Prospect, Tentative, Definite, Lost or Canceled. Each tentative booked space carries a hold rank such as H1 or Option 1, and venues can rename the statuses to their own terms, such as pencil or confirmed. Enterprise and Priava have their own versions. Map every status and every rank to the new system’s hold tiers, and agree the mapping with the sales team before any data moves. A hold that changes meaning in transit changes who wins the date.

Approvals. If some spaces need sign-off, record which ones and who approves, so the rule moves with the space rather than living in someone’s memory.

5. Future bookings versus history

Not everything needs to move.

Migrate future bookings at every status, open enquiries, active accounts and contacts, and anything with money still outstanding. This is live work, and staff need it in the new system on day one.

Archive completed events, closed enquiries and old financials to a read-only store your team can search, kept for as long as your record-keeping obligations require. Moving years of history into a new model costs a lot and buys little, because old statuses and spaces rarely map cleanly anyway.

Set the line per venue at its cutover date: future bookings, open enquiries and anything with money still outstanding move, whatever their date, and everything else stays in the archive.

6. Run venue by venue, not a big-bang cutover

A network-wide switch on a single date is the most commonly proposed approach and the riskiest. If anything goes wrong, every venue is affected at once.

We recommend moving one venue at a time, with both systems kept in step through each transition:

1. Pick the first venue carefully. Choose a quieter calendar or a quieter season, not your flagship in its busiest month.
2. Set its cutover date. From that date, the new system is the system of record for that venue, and new bookings are made there first.
3. Migrate its future bookings and reconcile them against the old system.
4. Keep the old system in step. Until the venue is signed off, mirror new bookings and changes back into the old system, so anyone still checking it sees the space as taken.
5. Run real events from the new system, with the old one available for reference.
6. Sign off and make that venue read-only in the old system, then start the next one.

It is slower. It is also the difference between a migration and an incident, and each venue makes the next one easier.

7. Train by role, not by module

Module training teaches people where the screens are. Role training teaches them how to do their job.

Group people by what they do: sales and bookings, event operations, approvers, finance, venue administrators, and leaders who only read. Teach each group the handful of tasks they do every week, using their own venue’s spaces and real bookings, as close as possible to that venue’s cutover.

Name a champion in each venue team who learns it first and answers questions on the floor. Then follow up after the first busy fortnight, because that is when the real questions arrive.

8. Integrations: finance, SSO, building systems, ticketing

Integrations usually belong to the organisation rather than to one venue, so they need their own transition plan.

• Finance. Momentus integrates with ledgers such as NetSuite, SAP, Oracle Financials, Microsoft Dynamics and Sage. While venues are split across two systems, decide which system posts which venue’s transactions, so nothing is posted twice or missed.
• Single sign-on. Momentus supports SSO via SAML. Connect the new system to your existing identity provider from the start, so there is no new account estate to manage.
• Building systems. If the building management system schedules HVAC, lighting or security from what is booked, point it at the new system venue by venue, and test it before that venue’s first event.
• Ticketing and other feeds. Elite offers a standard Tessitura integration, and custom integrations such as a website data feed and digital signage. List every system that reads from or writes to the booking system, and decide, per venue, which system feeds it during the transition.

9. Decommission

Switch the old system off only when every one of these is true:

1. Every venue has been signed off on the new system.
2. A final full export has been taken, checked against the source and stored.
3. The archive is searchable by the people who need it.
4. Every integration points at the new system.
5. Notice has been given exactly as the contract requires.
6. The vendor has confirmed in writing what happens to your data, and when.

Then remove user access and complete whatever else your contract asks of you. Done well, nobody outside the project notices the day it happens.

Where Booka fits

Booka is the venue management software we built for stadiums and venue networks. It covers the parts of this plan that are hardest to map: tiered provisional holds, conflict detection across a space hierarchy, approvals, staffing rosters, run sheets, per-venue access, an audit log and an external API to the building management system.

Booka is available to license for other stadiums and large venues, and Shakewell is a Registered supplier under the NSW ICT Services Scheme. For the wider market, see venue management software in Australia, and for the requirements to check any replacement against, what a venue booking system actually needs.

---

Sources: Momentus Momentus Answers (product lineage, implementation timelines, contract terms, Momentus Connect, SSO, finance integrations); Momentus Enterprise API (GitHub); Momentus Elite help centre: Momentus Elite and Integrations, All About Status, View Combo Rooms on the Calendar and Run a Report; Momentus Priava sell sheet (Momentus); Ungerboeck rebrands as Momentus Technologies and Ungerboeck and EventBooking announce merger (Ausleisure); Ungerboeck acquires Priava (Sports Venue Business); NSW ICT Services Scheme (buy.nsw).