> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/membership-management-hub/upgrade-member.md). # How to Upgrade a Member to a New Program Upgrading moves a member from their current membership program to a different tier. There are two ways to do it — **automatically** (age-based) or **manually** — and the method determines whether the member keeps their existing **membership ID**. ### Before you begin (Prerequisites) * **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **Target program**: The program you're upgrading the member into must already exist. See: [How to Create a Membership Program](/products/control-panel-overview/membership-setup-overview/create-membership-program.md). * **For age-based upgrades**: The age tiers must be configured first. See: [How to Set Up Age-Based Membership Transitions](/products/control-panel-overview/membership-setup-overview/set-age-transitions.md). ### Automatic upgrade (age-based) When age-based transitions are configured, the system upgrades the member on their birthday — no manual step required. * The member **keeps the same membership record**, so their **membership ID stays the same**. * The old card is marked **Upgraded**, and the subscription moves to the new program, matching the member's existing billing frequency (e.g., monthly vs. annual). See: [How to Set Up Age-Based Membership Transitions](/products/control-panel-overview/membership-setup-overview/set-age-transitions.md). ### Manual upgrade 1. Open the member's profile — navigate to [**MEMBERS > View Members**](https://control.peoplevine.com/membership/0/members), search for the member, and click **Edit** next to their membership. > **Note (Pro Dash):** Navigate to **REWARD > Members > All Members**. 2. Choose the right method for the membership type: * **ID Card membership (no-charge, no subscription):** Click **(Change Membership)** next to the program name and select the new program. * **Paid Subscription membership:** Do **not** use **(Change Membership)** — it will most likely break the subscription. Instead, **cancel the current subscription** (which cancels the membership) and **re-enroll** the member in the new program. This preserves historical tracking. See: [How to Enroll a Member](/products/control-panel-overview/membership-management-hub/enroll-member.md). ### Keeping the same membership ID * **Automatic (age-based) upgrades** retain the member's ID automatically. * **Manual re-enrollment** creates a *new* membership, so the **Membership Number auto-generates a new ID unless you set it**. To keep the member's existing ID, enter (copy and paste) their current **Membership Number** when re-enrolling — leaving it blank generates a new one. The **Membership Number** field also remains editable on the membership card afterward. > **Check-in**: Members check in by scanning their **membership card**, which carries their Membership Number. Keeping the same Membership Number on the upgrade keeps their check-in identifier consistent. If a new number is generated, have the member download their new card from the Member Portal under **Account > Memberships** (see [How to Send a Member Their Digital Membership Card](/products/control-panel-overview/membership-management-hub/send-membership-card.md)). Staff can also look the member up by name in the Check-In App (see [How to Look Up a Member Manually](/products/check-in-app-overview/manual-lookup.md)). > **Integrations**: **Access control and booking integrations** identify a member by their **CRM profile**, which doesn't change on upgrade, so those links stay intact. **POS/loyalty (e.g. Toast)** recognizes members by their **membership ID** — so re-use the same Membership Number to keep loyalty recognition seamless. If a member ever looks out of sync in a connected system, re-sync them with **Push Member** on their profile. See: [How to Push Members to Integrations](/products/integrations-overview/push-member-to-integrations.md). ### What Happens Next * **Perks**: When a member moves to a new program, the old program's perks stop re-issuing, but any already-issued perks (guest passes, vouchers) remain on the member's profile. The new program's perks begin issuing on the new schedule. To clear outstanding perks from the old program, manually redeem them from the member's profile. * **Related**: [How to Edit a Membership](/products/control-panel-overview/membership-management-hub/edit-membership.md) · [How to Enroll a Member](/products/control-panel-overview/membership-management-hub/enroll-member.md) · [How to Set Up Age-Based Membership Transitions](/products/control-panel-overview/membership-setup-overview/set-age-transitions.md). *** *Last updated: 2026-07-08* --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/control-panel-overview/membership-management-hub/upgrade-member.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.