This article is about the Proxi admin app at app.proxi.co, and the experience editor released September 15, 2026. Not sure which you have? Open your experience's participation link, the one participants use. If it starts with app.proxi.co, this is the right article. If it starts with map.proxi.co, yours is a legacy experience; look for the legacy article instead.
Running the same hunt in a second town, or rerunning last year's passport? You don't have to build it again. When your workspace already has experiences, the New Experience screen opens with one question, How do you want to start?, and three answers:
Start fresh — pick a type and a template, or start from scratch. This is the walk-through in Create Your First Experience From a Template.
Copy one of yours — places, clue cards, rewards and settings all come along; you pick the name and dates.
Bring in one from the old editor — for a legacy experience (its participation link starts with map.proxi.co). Stops, clue cards, badges and the sign-up form come over; you choose where its places come from.
If you came in from a type's own page ("New Scavenger Hunt"), only experiences of that type are offered to copy or bring in.
Copy One of Yours
Say your "Downtown Holiday Hunt" went well and the next town over wants one too.
Under Starting From, pick the experience to copy.
Town (optional) — type the new town and pick it from the list. Places that are connected to your listings come along as a fresh collection dropped at the town center, so you only have to drag the pins into place. Leave it blank to keep the same places.
Name is pre-filled as "<original> copy"; type a real one.
Set Starts and Ends, then create it.
Everything about how it plays comes with it: clues and clue cards, check-in rules, activities, badges (with fresh ids, so the copy's badges are its own), raffles, branding, tab names, and the sign-up page. A few things start clean on purpose: the web address and Join Code (the copy gets its own), participants, and anything on the Fundraising tab — the heading comes over, the items you sell don't, since each is tied to a payment product. Set those up again on the copy.
Bring In One From the Old Editor
This makes a new-editor experience out of a legacy one. The legacy experience isn't changed, and it keeps running; think of it as a copy into the new editor.
Under Which one?, pick the legacy experience. We read it and show what we found: the stops, badges, and sign-up questions.
Answer Where should the places come from?:
Use my listings — the best choice when the businesses are already listings in your workspace. Under Which listing stands in for each old stop? we suggest a match for each stop; fix any that are wrong.
Copy the places — makes a fresh collection with a copy of each old stop.
Keep the same places — points the new experience at the old map's places as they are.
Give it a Name and bring it in.
What comes over, and how it lands:
Stops keep their check-in codes and point values. A stop with nowhere to land (no listing picked, no place to copy) is left out, and we tell you how many.
Clues and clue cards come over as clue stops.
Badges keep their rules and thresholds exactly: "earn 20 points" stays 20 points, "visit 5 places" stays 5. Prize links and redeemable prizes carry over too.
The sign-up form asks what the old one did: the same required fields, your custom questions, and the opt-in checkbox if you required one.
Dates start today and run as long as the old one did (or with no end date, if the old one had none). Change them on the General tab.
The About text is brought over as written, so it may mention old button wording ("REVEAL", "+ collect") or last year's partner. The A few things worth a look list on the import screen points these out; give it a quick read before you publish.
Good to Know
Both paths create a draft. Nothing is live until you Publish. (See Going Live, Pausing, and Publishing Changes.)
Participants never move. The old experience keeps its people and their progress; the new one starts empty.
Legacy experiences keep working with nothing to migrate. Bringing one in is for when you want the new editor's features for the next run, not something you have to do.