# Moving Existing Members to a New Price Structure

HTML version: [Moving Existing Members to a New Price Structure](https://support.gladstonesoftware.cloud/gooperator/moving-existing-members-to-a-new-price-structure)

## Problem
You are introducing new subscriptions and price levels for Gladstone Go and need to decide what happens to existing members who are still on the old subscriptions and price levels.

## Resolution

1. **Decide whether to move existing members at all**
   - Existing members can stay on their old subscriptions and price levels: the old configuration keeps working, and new sales use the new subscriptions. Old subscriptions then run down naturally.

2. **Prepare a mapping (if moving everyone)**
   - To move everyone onto the new subscriptions, the Gladstone data team runs a **data import** from a mapping (old subscription → new subscription).
   - Members who share one old subscription but belong to different groups (for example, staff, alumni and 60+) can only be split if something on the record (for example, a user field) identifies them reliably, so check data quality first.

3. **Ask for the new price levels to be scripted onto products (if applicable)**
   - The data team can also script the new price levels onto products: tick *Purchase allowed* on all resource products (IDs starting Z/ZZ) and set prices and tax codes on price products from the existing standard price.
   - Give them a list of products with price level overrides. These must be excluded and done by hand.

## Notes

- Test the new structure before go-live: see [Testing Gladstone Go Before Go-Live](testing-gladstone-go-before-go-live.md).
- Related: [Go Configuration Build Order Across Products](go-configuration-build-order-across-products.md).