Moving to a New Event Photo Platform Without Breaking Guest Access

You can move to a new event photo platform without breaking guest access, but only if you treat every old link as permanent. Export the photo files, keep the old galleries live for 60 to 90 days after the new platform goes live, and accept that face matching data and per-guest match history do not carry across, so guests take a fresh selfie on the new platform. The part that actually breaks migrations is not the photo export, it is a QR code already printed on badges and signage, pointing at a vendor domain you do not control.

Find every place your old link is printed or pasted before you export a single photo

The photo library is the easy part. The hard part is every place that old link already lives. Your old platform's dashboard lists the galleries it hosts; the pasted, forwarded and printed copies of that URL sit outside it. Spend the first afternoon building that list, because it decides which of the four migration approaches below you can afford.

Some surfaces are easy to miss. Search your own website for the vendor's domain, search your sent mail for the same string, and ask marketing and the sponsorship lead, because they publish links you never see.

• Guest WhatsApp groups, where a gallery link gets forwarded for weeks and there is no way to unsend it
• The post-event thank-you email, which sits in inboxes and stays searchable
• LinkedIn and Instagram recap posts, yours and your sponsors', often with the link in the first comment
• Your own event page, the venue's page, and any partner or association write-up
• Printed items: roll-up banners, table talkers, badge backs, welcome desk cards, and screens whose slide deck lives with the AV company
• Internal wikis, SharePoint pages and the shared asset folder the next edition gets built from

Four ways to move, ranked by how much guest access you risk

There are four approaches, set out in the table below in order of risk: hard cutover, parallel run, archive freeze and forward-only. Migrating everything is the expensive default, worth testing first. Open your old platform's analytics and look at which galleries are still receiving visits, the only evidence about your own events that anyone has. The way that traffic concentrates around the event is the mechanism behind the 24-hour social window, and the reason long-tail archive access is worth less than it looks.

Match the approach to where your links live. If nothing was ever printed and the only link went out in one internal email thread, a hard cutover is fine. If you run an annual conference with reusable signage, a hard cutover puts every printed code on a dead URL, and a parallel run is the honest cost of the switch.

What transfers between platforms, and what never does

Expect the photo files to come across, and plan to rebuild everything else by hand. Before you export, check the pixel dimensions of what you get back against the originals, because some exports contain only the display copy, which shows up when a file goes to print. The safer source is your photographer's delivery drive. If the only surviving copy of an event's photos is on a vendor's servers, that is a bigger problem than the migration you are planning.

• Transfers with effort: the photo files, album and folder structure, event names and dates, sponsor logos and branding assets, and your own guest email list wherever your CRM holds the master copy
• Never transfers: face matching data, a private mathematical signature of each guest's face. Every platform generates and stores it in a format of its own, so an export would be meaningless to the next one - and you should not want to receive another company's biometric records
• Never transfers: per-guest match history, so a guest who already found their photos on the old platform searches again on the new one
• Never transfers: the personal album URL each guest bookmarked or saved to their home screen
• Capture before you cancel: view, download and share analytics. These numbers exist only inside the old account, so once it closes there is no way to produce them for a sponsor report. Export the consent log too: evidence you keep for your own records, with no use to the new platform

Consent does not port cleanly, so plan to ask again

Under the UK and EU GDPR, matching faces to identify individual guests is special category processing, and at an event explicit consent is the workable basis. The UAE and Saudi personal data protection laws and India's DPDP Act also require consent for this processing, with different definitions and notice rules, so check the wording against the country the event is held in. Whichever regime applies, the consent your guests gave covered a specific processing arrangement, described in a notice that named a specific processor. Swap the processor and that notice is out of date.

The clean answer is to re-notice and re-ask on the new platform, which is lighter than it sounds: a guest arriving at a migrated gallery takes one selfie, is matched straight away, and consent is captured at that moment with a current notice behind it. The cost is one extra step for guests who already found their photos once, a further argument for migrating only the events still receiving visits. Our event photo consent guide and GDPR and facial recognition at events cover the notice wording.

Printed QR codes are the only genuinely irreversible part

A QR code is a fixed string. Once it is on the badges, the roll-up banner and the table cards, the destination is set for the life of those objects. If that string is oldvendor.com/your-event, you have exactly one option: keep the old gallery alive until every printed item is out of circulation. For a one-off gala that is a few weeks. For an annual conference, the signage lives in a storage crate between editions and comes back out still carrying the old URL.

The fix takes an afternoon if you already own a domain, and it only helps you next time. Print QR codes that resolve through an address you control, such as photos.yourbrand.com/summit26, and point that address at whichever platform you are using. Change vendor later and the whole job is one redirect rule. If you are still deciding how guests reach their photos, QR code versus selfie search covers the entry point itself.

Where other tools genuinely beat an event platform

An honest point, because it changes what you migrate. A shared Google Drive or Dropbox folder is about as portable as event photos get: there is no gallery vendor in the relationship at all, and no expiry while you pay for the storage. It has no selfie search, no per-guest album and no sponsor analytics, so it loses badly on the day of the event. As a cold archive it wins, and that trade-off is set out in Google Drive versus AI photo delivery.

Photographer gallery tools are a different category again. That category is sold as ongoing storage subscriptions, so a gallery stays reachable while the subscription is paid, and the storage allowance decides how many years you can keep up. Pixieset and Pic-Time are the two names to price up against that requirement, from their own pricing pages. Event platforms, Eventiere included, are built around the event and the days immediately after it. Our free plan gives you three events, 300 photos in total and 100 photos per event with no credit card, and expires galleries after 30 days; our paid plans are quoted per event. If your requirement is keeping four years of galleries reachable, an event platform is the wrong tool.

A four-week plan, and what to get in writing before you cancel

Do this in your quietest four weeks, whenever those fall in your calendar. What you need is a window with no live event on top of you, and four weeks is enough if you keep the scope honest.

Go-live is the end of Week 3, Day 21 of the plan, when the new links go public. The 60 to 90 day overlap runs from that date, so the earliest you can close the old account is Day 81 and the full 90 days takes you to Day 111. The single rule that saves migrations: never cancel inside 60 days of launching the new one. Overlap costs you two or three more months on the old platform, and even counted from Day 1 of the plan the double-paying stretch is under four months. Cancelling early costs you every circulating link at once, with no way to get them back.

• Week 1: build the link-surface list, export the photo files, pull originals from the photographer wherever the export is downsized, and screenshot analytics and consent logs
• Week 2: rebuild only the events your analytics show are still receiving visits, then test with five colleagues taking selfies on their own phones and their own mobile data, away from the office Wi-Fi
• Week 3, ending Day 21: publish the new links everywhere you control, leaving every old link live and untouched: website, email footers, sponsor recap pages and the internal asset folder. The overlap clock starts here
• Week 4: point your next event at the new platform and brief the photographer and the AV company on the new entry point
• Day 81 at the earliest, Day 111 for the full 90 days, later again if printed items are still circulating: request written confirmation that photos and face matching data have been deleted, and ask for the backup retention window in writing, because deletion from live systems and deletion from backups happen on different clocks. Only then cancel

Keep reading