> 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-setup-overview/set-age-transitions.md).

# How to Set Up Age-Based Membership Transitions

### 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).
* **Both Programs**: The source program (e.g., Junior) and target program (e.g., Full Membership) must both exist. See: [How to Create a Membership Program](/products/control-panel-overview/membership-setup-overview/create-membership-program.md).
* **Birthdate Data**: Member CRM profiles must have accurate birthdates for age calculations to work.

### Instructions

1. Navigate to [**MEMBERS > Manage Membership Programs**](https://control.peoplevine.com/admin_membership_list.aspx).

> **Note (Pro Dash):** Navigate to **REWARD > Manage Membership Programs**.

2. Click **EDIT** next to the **source** program (the one members will transition out of).
3. Expand the **Settings** section.
4. Configure the age fields:

| Field                                    | What to Enter                               | Example         |
| ---------------------------------------- | ------------------------------------------- | --------------- |
| **Min Age**                              | Minimum enrollment age                      | 18              |
| **Age Out**                              | Age at which transition fires               | 35              |
| **When they reach this age, upgrade to** | Select the target program from the dropdown | Full Membership |

5. Click **UPDATE MEMBERSHIP**.

### How transitions work

When a member turns the age set in the **Age Out** field, the system automatically:

* Creates a new membership card on the target program
* Marks the old card as **Upgraded**
* Transfers the subscription to the new program, matching the billing frequency where possible (if no exact match, defaults to annual, then monthly)

The system also fires a **Member is Older** trigger that can be used for newsletter and campaign notifications.

### Common transition scenarios

| Source Program              | Age Out | Target Program      |
| --------------------------- | ------- | ------------------- |
| Junior Membership (18--35)  | 35      | Full Membership     |
| Young Professional (21--40) | 40      | Standard Membership |
| Full Membership             | 65      | Senior Membership   |

### Best Practice

Make birthdates a required field during application or enrollment. Age transitions only work if birthdates are accurate in CRM profiles — missing data means the system cannot trigger the transition.

### What Happens Next

* **On the system side**: The system monitors member birthdates and automatically transitions members when they turn the age specified in the Age Out field. The member's subscription updates to the new program with adjusted pricing.
* **Next step**: Test the configuration by verifying that age fields are set correctly on staff profiles before relying on automatic transitions for live members.

*Last updated: 2026-05-24*


---

# 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-setup-overview/set-age-transitions.md?ask=<question>&goal=<endgoal>
```

`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.