> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/miscellaneous/what-should-i-do-when-my-business-or-location-changes-ownership.md).

# What should I do when my business or location changes ownership?

If a Perkville business or location is changing ownership, plan the handoff before the effective date. An ownership transfer can involve staff access, billing responsibility, payment information, contract details, and integration configuration, so it is broader than simply changing a password or replacing one staff member.

{% hint style="warning" %}
Do not share a former owner's or employee's Perkville credentials with the incoming team. Each authorized staff member should use their own account.
{% endhint %}

## 1. Contact Perkville before the ownership change

Contact [Perkville Support](https://docs.perkville.com/overview/support.md) and provide:

* The business or location changing ownership.
* The effective date of the change.
* The current owner's contact information.
* The incoming owner's contact information.
* Whether the change affects billing, the business entity, locations, or the connected POS/membership system.

This gives Perkville time to identify any account, subscription, contract, or integration steps that require assistance.

## 2. Give the incoming team its own Admin access

Before removing the current owner or other departing staff, make sure an authorized member of the incoming team can sign in with the **Admin** role and has access to the correct locations.

See [Staff members](https://docs.perkville.com/features/settings/staff-members.md) for adding staff, assigning roles, and limiting access by location.

## 3. Transfer billing responsibility and update payment information

If the departing owner or employee is the billing-responsible user, assign billing responsibility to another authorized staff member before removing them.

Then review the payment method on file. See [How do I update my billing information?](https://docs.perkville.com/faqs/miscellaneous/how-do-i-update-my-billing-information-e.g.-credit-card-on-file.md).

{% hint style="info" %}
Changing the billing-responsible staff member or payment method does not by itself update contract or account ownership. Contact Perkville Support for ownership-related account or contract changes.
{% endhint %}

## 4. Review location and integration configuration

If the ownership change also changes the location's POS, membership system, account/site identifier, or integration authorization, coordinate those changes with Perkville before cutover.

See [Locations](https://docs.perkville.com/features/settings/location-setup/locations.md) and the [Integration Reference](https://docs.perkville.com/integrations/integration-reference.md) for the relevant configuration pages.

## 5. Remove departing staff after the handoff is complete

Once the incoming team can sign in and billing responsibility has been transferred, remove staff who should no longer have access.

See [When a staff member leaves or nobody can access the account](https://docs.perkville.com/features/settings/staff-members.md#when-a-staff-member-leaves-or-nobody-can-access-the-account).

## 6. Review customer-facing program changes

If the new owner plans to change earning rules, rewards, participating locations, or other program terms, make those changes deliberately and communicate any customer-facing changes before they take effect.

For a location that is leaving Perkville rather than continuing under new ownership, see [How do I stop customers from earning new points but let them use existing points?](https://docs.perkville.com/faqs/points/how-do-i-stop-customers-from-earning-new-points-but-let-them-use-existing-points.md#winding-down-one-location-in-a-multi-location-program).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/faqs/miscellaneous/what-should-i-do-when-my-business-or-location-changes-ownership.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
