Amelia 9.7: Public Event Pages, Full Data Export & Import, and More

Amelia 9.7 is here, and it brings a few updates that can make a real difference in how you promote events, manage your setup, and deliver a smoother booking experience.

Some changes are designed to save you time behind the scenes. Others make it easier for customers to find what they need and complete a booking without unnecessary steps.

Let’s take a closer look at what’s new.

Public Event Pages

Every Amelia event now gets its own dedicated public page with a unique URL. One page, one event, one clear path to booking.

Think about what that means in practice. You’re running a workshop next month. Instead of sharing a link to your full event calendar and hoping people find the right one, you drop a single link straight to that workshop. It shows the event image, full timetable, description, ticket options, and a Book event button. Nothing else to navigate, nothing else to figure out.

This is the link you put in your Instagram bio the week before the event. It’s what you include in your email newsletter. It’s what you send to the Facebook group you’re promoting to. A focused, self-contained page that does one job: get people to book.

It works especially well for event creators who promote individual events rather than a whole schedule, like fitness instructors pushing a one-off masterclass, educators launching a new course date, or venues promoting a ticketed evening. Anywhere you’d naturally want to highlight one specific event without the noise of everything else around it.

The public event page is available on all Amelia plans, including Lite.

📖  Read the full documentation → Public Event Page

Data Export & Import

Moving your Amelia setup between sites has always been more painful than it should be. Manually recreating services, employees, settings, notifications, it all adds up fast. With 9.7, you can export everything into a single file and import it somewhere else.

The export covers your full dataset: bookings, customers, settings, notification logs, SMS history, and more. Everything packed into one .AMELIAFILE, ready to drop into another site.

The most common use case is migrating from a dev site to production. You build out your whole setup in a safe environment, test everything until it’s right, then move it live without rebuilding from scratch. Same goes for the other direction; you can clone a live site into staging so you can test a new feature or a bigger change before it touches your real bookings.

It’s also useful if you’re managing Amelia for clients. Set up a base configuration once, export it, and use it as a starting point for the next site rather than starting from zero every time.

A couple of things to keep in mind: both sites need to run the same Amelia version and license type, and the import always replaces all existing data, so back up before you run it.

📖  Read the full documentation → Data Export & Import

Improvements

Year added to event date in the Event List. Event dates now show the year alongside the day and month. This is a small change that makes a real difference when you’re running recurring events across multiple years.

WCAG accessibility improvements. The Date Range picker, the Employee panel, and the Catalog booking form have all been updated to comply with WCAG standards. Better keyboard navigation, improved screen reader support, and a more inclusive booking experience for your customers.

What’s Next?

Amelia 9.7 is all about removing unnecessary steps, whether you’re promoting an event, moving a setup between websites, or helping customers complete a booking.

And we’re not stopping here.

We’re already working on 9.8, and it’s shaping up to bring some long-requested improvements around calendar syncing, a smoother way to preview your booking form directly inside your favorite page builder, and more flexibility for teams managing multiple client sites. More details soon.