The risky part of an upgrade comes after the donor says yes

Before you ask monthly donors to increase their gifts, prove that one donor can complete the change safely. The original recurring plan should remain identifiable, the donor should see the new amount and effective date before confirming, and your team should be able to verify what changed.

If that path does not work from appeal to next charge, fix it before sending the campaign. A persuasive ask cannot repair a duplicate subscription or an unclear confirmation.

Start with an upgrade contract

A monthly-donor upgrade is a change to an existing recurring commitment. Treat it as a small operating contract with four parts:

1. Eligible subscription: the recurring plan is active and has no unresolved payment or change issue.
2. Authorized path: the donor can approve the increase through a control your platform supports.
3. Visible effective date: the donor and your team can see the new amount and when it begins.
4. One closeout record: the response is linked to the original subscription and the upgrade campaign.

This is a readiness test, not a universal campaign formula. Your platform controls which changes donors can make themselves, which changes staff may perform, and whether an amount update modifies the current plan or requires another supported path. Route a donor-initiated change through the platform you actually have, then use the same verified path in the campaign.

Prove the path before writing the appeal

Run one complete upgrade with an internal or otherwise authorized test record. Start from the message or page a donor will receive. Finish only after your team can inspect the updated recurring plan.

The test should answer five questions:

• Did the link or portal open the intended donor's recurring plan?
• Did it show the current amount, proposed new amount, and effective date before confirmation?
• Did the donor take an explicit confirmation action?
• Did the original subscription change without creating a second active subscription?
• Did both the donor-facing confirmation and staff record agree?

Current platforms implement this differently. Fundraise Up documents personalized upgrade links that let a recurring supporter review and confirm a higher amount without re-entering payment details. Its documentation also warns that an authenticated link must reach the intended supporter because a misdirected link could change someone else's plan. That is one vendor's model, not a feature you should assume elsewhere.

If the test creates a second subscription, hides the effective date, or leaves no staff-visible change record, stop. Record the failure and assign an owner. Do not ask donors to discover it for you.

Build the audience from active records

The campaign audience should begin with subscriptions that can actually follow the tested path. Use a saved rule that your team can rerun before each send. At minimum, require:

• an active recurring plan with a known current amount and schedule;
• a valid contact route that belongs to the same donor;
• no open cancellation, pause, amount-change, or payment-recovery task; and
• no completed upgrade from this campaign.

Hold records that fail one of those checks. A donor in a retry sequence needs the next action from the failed recurring donation workflow, not a crossed upgrade request. A donor with an unresolved change needs that request closed first.

Do not invent an ideal donor tenure, increase percentage, or campaign frequency. Choose the audience and ask from your own program, capacity, and current gift history. The operational gate is simpler: every included donor must have one clear current plan and one supported way to authorize the proposed change.

Keep the campaign and subscription connected

The campaign record explains why you asked. The subscription record explains what the donor authorized. Do not force either record to do both jobs.

For each response, preserve the campaign or message version, response date, original recurring-plan ID, previous amount, new amount, effective date, confirmation state, and closeout owner. Salesforce's current recurring-donation guidance illustrates this separation by recording an upgrade against the existing recurring donation while retaining the previous amount, new amount, effective date, campaign, and change history.

Your field names will differ. The boundary should not: one campaign response points to one documented change on one recurring plan.

Close each response before the next ask

Give every campaign record one of four outcomes:

• Upgraded: the original subscription shows the confirmed new amount and effective date.
• Declined or no response: no subscription change occurred.
• Needs help: the donor responded, but a supported change still needs an owner.
• Path failed: the donor tried, but the link, portal, confirmation, or staff record did not complete correctly.

Remove upgraded donors from later upgrade asks in the same campaign. Keep declines and nonresponses separate; silence is not authorization to change a recurring gift. Route failures to an exception queue instead of sending the same link again without diagnosis.

Then compare the campaign response count with the subscription change log. The totals do not need to be equal because some donors may decline or take no action. Every reported upgrade does need a matching change on the original recurring plan.

Make one record pass before launch

Your upgrade campaign is ready when one authorized test proves the complete path: the intended donor opens the right plan, sees the old and new terms, confirms the increase, keeps one active subscription, receives a clear confirmation, and appears in the staff change record with the correct effective date.

If any part is missing, the campaign is not ready. Fix the path first; then decide the audience, amount, and message.