---
title: Transferring an Application to Another Event
description: "VendorHearth Pro allows organizers to move a vendor application from one event to another. This can be useful when an application needs to be associated with a different event without requiring the organizer to manually recreate the vendor's information. ##…"
url: "https://vendorhearth.com/docs/transferring-an-application-to-another-event/"
updated: "2026-09-23"
category: "Applications & Waitlists — application review, approval/decline, Request More Information, transfers, waitlists"
---

# Transferring an Application to Another Event

VendorHearth Pro allows organizers to move a vendor application from one event to another.

This can be useful when an application needs to be associated with a different event without requiring the organizer to manually recreate the vendor's information.

## When to Transfer an Application

An application transfer may be appropriate when:

- A vendor applied to the wrong event
- A vendor needs to move to another upcoming event
- An organizer needs to correct the event associated with an application
- Another event is a more appropriate destination for the application

The transfer feature keeps this process within VendorHearth.

## Transferring an Application

To transfer an application:

1. Go to **VendorHearth Pro → Applications**.
2. Locate the application you want to move.
3. Open the available application actions.
4. Select the option to transfer or move the vendor to another event.
5. Choose the destination event.
6. Review the transfer information.
7. Confirm the transfer.

After the transfer, verify that the application is associated with the correct event.

## Review the Destination Event First

Events can have different configurations.

Before transferring an application, check the destination event's:

- Booth types
- Booth pricing
- Booth capacity
- Vendor categories
- Category limits
- Application requirements
- Agreements
- Paid Add-Ons

An option that was available for the original event may not exist or may not be available for the destination event.

## Check Booth Availability

Do not assume that the vendor's original booth request can automatically be accommodated at the new event.

The destination event may have different booth types, prices, or capacities.

Review the vendor's booth information after the transfer and make any necessary adjustments.

## Check Category Availability

Category limits are also event-specific.

A vendor's category may have been available at the original event but already be full at the destination event.

Review category availability before completing the vendor's approval process for the new event.

## Review Payment Information

Transferring an application does not mean that historical payment information should be rewritten or recreated.

If payment has already occurred, review the vendor's payment record and determine what administrative action is appropriate for the transfer.

VendorHearth payment records should reflect transactions that actually occurred.

Do not create a false payment simply to make the transferred application appear paid.

## Review Agreements

Different events may have different agreement requirements.

Transferring an application does not fabricate a new agreement acceptance.

If the destination event requires an agreement the vendor has not accepted through the appropriate workflow, that requirement should still be completed.

## Review Booth Assignments

If the vendor had a specific booth assignment at the original event, verify their booth information after transferring the application.

A booth number from one event should not automatically be treated as a valid location at another event.

Assign or allow selection of an appropriate booth for the destination event.

## Verify the Application After Transfer

After transferring an application, open it again and review:

- Destination event
- Application status
- Booth information
- Category
- Payment information
- Agreements
- Any event-specific requirements

This final review helps catch differences between the original and destination events.

## Transfer vs. Creating a New Application

Use the transfer feature when an existing application genuinely needs to be moved to another event.

If the vendor intends to participate in **both** events, do not transfer the original application away from the first event.

The vendor should have the appropriate application or participation record for each event.

## Preserve Accurate History

Application transfers are administrative tools for correcting or moving an application.

They should not be used to make payment, agreement, or participation history appear differently from what actually occurred.

VendorHearth's records are most useful when they accurately reflect each vendor's activity.

## Next Step

Continue to **Importing Existing Applications** to learn how VendorHearth can bring existing vendor records into the system while preserving accurate payment and agreement history.