---
title: "Exporting Gomry Data Before You Change Software"
meta_description: "Export contacts and registrations from Gomry through Aven or the dashboard, retrieve related records through the API, and preserve customers’ paid access when switching."
canonical: "https://business.gomry.com/blog/export-gomry-data-before-switching/"
comparison_date: "2026-10-12"
sources: ["https://docs.gomry.com/introduction","https://docs.gomry.com/scopes","https://docs.gomry.com/pagination","https://docs.gomry.com/api-reference/contacts/list-contacts","https://docs.gomry.com/api-reference/lists/list-lists","https://docs.gomry.com/api-reference/attendees/list-attendees","https://docs.gomry.com/api-reference/ticket-classes/list-ticket-classes","https://docs.gomry.com/api-reference/applications/list-applications","https://docs.gomry.com/api-reference/payments/list-payments","https://docs.gomry.com/api-reference/experiences/list-experiences","https://docs.gomry.com/api-reference/recurrences/list-recurrences","https://docs.gomry.com/mcp/setup","https://docs.gomry.com/mcp/tools","https://docs.gomry.com/rate-limits","https://www.gomry.com/docs/business-terms"]
cta_label: "Read the API documentation"
cta_url: "https://docs.gomry.com/introduction"
---

# Exporting Gomry Data Before You Change Software

You can take your customer records and booking information with you when changing software. Aven can prepare downloadable CSV files of your organization’s contacts or an Event’s participants. For Experiences, the dashboard exports the full booking history. Developers can also retrieve related records through Gomry’s API, while connected assistants use the tools available through Gomry MCP.

When changing booking systems, the new provider also needs to recognize the places customers have reserved and the visits they have already paid for. Keep Gomry’s identifiers alongside readable names so a payment, registration and form response can still be matched after export. The customer list and those existing commitments need separate treatment.

## Get CSV files from Aven and the dashboard

Aven delivers its exports directly in chat as secure download links. The contacts export contains the organization’s CRM records, including personal details, email addresses, opt-ins and aggregated history. An Event participant export includes names, email addresses, ticket types, purchase dates, registration status and answers to the registration form’s custom questions.

For example, an organizer moving a workshop’s registrations can ask:

“Export the full participant list for our October Pottery Workshop as a CSV, including ticket types, purchase dates, registration status and answers to the registration questions.”

Aven needs the correct Event, not just a name that could match several workshops. The example names a fictional event; the export covers that Event’s participant list, not every registration in the organization.

Experiences have a separate dashboard export. Open the relevant Experience, go to Registration / Attendees and choose Export CSV. This returns the full booking history rather than the first 100 bookings available in chat. Use it when moving a recurring class with hundreds of reservations.

Aven also exports Event traffic reports. These include referrers, all five UTM tags, page views, unique visitors and daily conversion history. They help retain marketing records, but do not replace the participant list or create access in the new system.

## Keep tickets, answers and payments connected

For an Event, export the event details and its ticket classes with the attendee records. The attendee API returns each ticket's identifier, ticket class, status, holder details, barcode and check-in timestamp. That lets you distinguish a valid ticket from one already checked in and retain the ticket type the guest purchased.

Registration answers are separate form submissions. Their records include the form ID, contact ID, answers and, where present, a linked payment ID. Each answer carries a question ID matching the form definition. Keeping both the question and its answer avoids turning a response such as “Yes” into a value with no context.

Payment records provide another connection: the event or product, amount, currency, status and linked form submission where available. The documented payment schema also includes a Stripe payment reference. That reference helps connect records; it is not a customer's saved card or permission to charge them again.

For example, a workshop organizer may have one purchase covering two guests. The payment records the purchase, while the attendee list identifies the ticket holders. Importing only the buyer's contact would not recreate both guests' admission. Retaining the related records gives the destination system the information needed to represent that purchase correctly.

## Retrieve structured records through the API

Gomry's API returns structured JSON rather than a ready-made import file for every destination. A developer can retrieve the relevant records and convert them into the format the new provider accepts.

| Records | What the documented interface provides | What to retain for the move |
| --- | --- | --- |
| Events and ticket classes | Event details, ticket types, prices and capacity | Event and ticket-class IDs alongside dates and names |
| Attendees | Ticket status, holder details, barcode and check-in time | Ticket ID, ticket-class ID and the event it belongs to |
| Contacts and lists | Contact details, lists and list membership | Contact and list IDs, not just an unlabeled set of email addresses |
| Forms and submissions | Questions, answers, applicant links and payment links where present | Form, question, submission and linked contact IDs |
| Payments | Amounts, currency, status, fees and related records where present | Payment ID, relevant event/product/application IDs and processor reference |
| Experiences and schedules | Recurring offering details and recurrence rules | Experience IDs, schedules, capacity and the terms of each offer |

An API key is created in Organization Settings → API Keys. It has permissions for individual resources, so an export can use read access without granting permission to change events or contacts. Reading contacts within a list requires access to both lists and contacts.

Paginated list endpoints return page and total-page information. A complete retrieval must follow those pages, not stop at the first response. Other endpoints have their own response limits. Filters matter too: payments default to successful transactions, while other payment states include refunded and failed. A history intended for reconciliation needs the relevant states, not only completed sales.

## Use Claude or ChatGPT for supported account tasks

Gomry MCP, the Model Context Protocol connection, lets compatible assistants such as Claude or ChatGPT use authorized tools in your Gomry account. The assistant can use the tools allowed by your role in each organization. It does not gain unrestricted access merely because it is connected.

For Event records, tools can read events, ticket classes, attendees, forms and payments. A connected assistant exposing the contact-export tool can also prepare a CSV of contact details, list and tag membership, and custom fields. That tool can filter by list, Space or name/email search. A Space is an organizational subdivision in Gomry.

The MCP contact-export tool asks for confirmation before exporting personal data and refuses selections above 2,000 records rather than silently returning a partial file. Use its filters for a defined customer group; use Aven’s Contacts export for the organization-wide CRM records.

Experience booking tools return at most 100 recent bookings, with a truncation indicator when more exist. For the full history, use the Experience dashboard’s CSV export described above. For a repeatable migration pulling several related collections, the API lets a developer control pagination and preserve the relationships across files.

Gomry charges no additional fee for API or MCP access and applies no commercial usage quotas. Technical request limits still apply: the API allows 60 requests per 10 seconds per IP address; MCP allows 120 requests per minute per user. An assistant subscription or another third-party service may have its own charges and limits.

## Preserve what customers can still use

A studio changing systems needs to distinguish a confirmed class booking from unused prepaid visits. The booking reserves a particular place. A Bundle supplies visits for selected Experiences, and a Subscription provides recurring class access under its purchased terms. Membership Levels represent organization-wide member status rather than a class visit balance.

In the new system, these rights need an equivalent representation. A customer's three unused visits, their expiry and the classes they cover belong with the balance; next Tuesday's confirmed place belongs with the booking. One should not be reconstructed from the other.

Review these rights in the Space’s Members and Bundles dashboards. Members contains the membership and recurring-access records; Bundles contains the prepaid packs. These records show status, balances and validity. Aven does not currently provide a chat export for these rights, so use the dashboard records alongside the participant files.

The original purchase is identified by its `orderCode` or `paymentId` in the payment register. The customer’s email or `userId` identifies the account holding the Bundle or Membership Level. Keep both connections: the transaction identifies what was purchased, while the account identifies who can use it.

In participant or booking CSVs, a reservation using prepaid or membership access carries the relevant `bundleId` or `membershipLevelId` in its payment method or type. Its monetary amount is 0 because the payment was collected for the original purchase, not again for that reservation. For a customer with three unused visits and next Tuesday already booked, the zero-value booking still reserves a place; it is not a free visit or evidence that the pack had no purchase price.

For Subscriptions, Gomry does not currently offer a direct automatic transfer of recurring payment agreements or saved card tokens to another platform. Export the member details and expiry dates from the Space’s Members register, cancel the Gomry renewals to prevent further charges, and send customers the new provider’s payment link. They need to enter their payment details and authorize the new recurring payment themselves. A historical payment reference remains useful for reconciliation, but does not authorize the new provider to charge the customer.

## Move the data, then reconcile the commitments

The destination provider's import format determines how exported records become usable there. A provider that accepts a contact CSV may still require separate preparation for reservations or remaining visits. The export gives you records; importing and checking those commitments completes the operational move.

Choose a cutover time and retain a final set of records from Gomry. Match imported customers to their future places and remaining purchases before directing them to the new timetable. If a ticketing or booking system cannot carry a particular entitlement, the organizer needs a supported way to honor it separately rather than allowing it to disappear in the customer-list import.

Keep the account active while settling those commitments. Close registration for Events to stop new sales. For Experiences, archive the offers and cancel future sessions as they are moved or withdrawn; cancel recurring subscriptions to stop further charges. Refund tickets or bookings for future services you will not provide, through the dashboard or Aven, then withdraw the remaining available balance once outstanding payments are settled.

Account deletion is the final step, not the migration tool. If you are the organization’s only Admin and there are pending payouts or active tickets for future Events, Gomry disables Delete Account. Save the records before closing your account: Gomry’s [merchant terms](https://www.gomry.com/docs/business-terms) state that termination ends your right to use the service and may remove access to your Events. Obligations already owed to customers or Gomry remain after termination.