Skip to main content
This guide walks you through preparing Portal V2, testing your organization’s donor experience, and switching donor traffic when you are ready. Your existing donor data, redirects, and portal settings automatically carry over to Portal V2. You do not need to import donors, recreate redirects, or rebuild your portal configuration. You will set up your Portal V2 appearance and review the experience before launching. Start with the shared setup steps below. Then follow the instructions for your current portal address:
  • Shared domain — your donors visit an address such as app.wegive.com/my-org-slug.
  • Custom domain — your donors visit an address your organization owns, such as give.my-organization.org.
If you use both kinds of addresses, follow both paths for the links and domains your donors use.

​
1. Coordinate with WeGive to enable Portal V2

Contact WeGive to enable Portal V2 for your organization. Enabling Portal V2 does not automatically move existing donor traffic to the new portal. It makes Portal V2 available to your organization and unlocks Portal V2-specific settings in the admin dashboard. Your existing V1 links and domains continue serving V1 until you take the cutover steps later in this guide. New links generated by the dashboard may point to Portal V2 once it is enabled. Wait until you have finished testing before publishing or sharing them with donors.

​
2. Set up your Portal V2 appearance

  1. In the admin dashboard, navigate to Profile → Portal Settings.
  2. Open the Portal V2 tab.
  3. Upload a Full Logo for your organization’s sign-in screen and desktop header.
  4. Select a default theme. If you do not have one yet, click Create a Theme to open the theme creation flow.
  5. In the theme’s Details tab, make sure Portal Default is enabled. This makes the theme the default appearance for your donor portal.
  6. Open the Brand tab to configure your organization’s colors.
  7. Review any other appearance settings you would like to customize, and save your changes.
A theme controls how your portal looks. In addition to your main colors, you can customize logo overrides, the favicon (the small icon in a browser tab), fonts, and light/dark mode behavior. You can also adjust success and error colors, rounded corners, icon colors, and button colors — including how buttons look when someone hovers over them. You do not need to customize every setting. Start with your logo and colors, then refine the appearance as you review the portal. If you offer both light and dark modes, check both. Individual custom domains or embedded elements can use a different theme. If you have assigned one of these overrides, review that experience separately — changing the portal default will not replace the override.

​
3. Follow the path for your portal address

​
Path A: Your organization uses the shared domain

​
Preview and test Portal V2

Visit https://portal.wegive.com/my-org-slug, replacing my-org-slug with the same organization identifier used in your existing portal address. Review your theme and portal settings, and complete the pre-launch testing checklist below. Test thoroughly before updating any public links or embeds. This is also the time to verify your analytics. Check that visits, completed donations, and campaign attribution appear as expected. Review any tracking rules that depend on the old portal address.

​
Switch donor traffic to Portal V2

When you are ready to launch, update your organization’s donor-facing links and embeds to use portal.wegive.com instead of app.wegive.com. Keep the organization identifier, page path, and any information after ? intact. For example: Check all the places donors might enter your portal, including:
  • Website donation buttons and portal sign-in links.
  • Embedded donation forms and popup donation buttons.
  • Email templates, automated messages, and scheduled campaigns.
  • Social profiles, advertisements, and QR-code destinations you can update.
Popup script note: The dashboard’s implement modal still provides a popup script URL on app.wegive.com, even after moving to V2. You can leave that script URL as generated and point the popup’s donation-page URL to Portal V2. Portal V2 also hosts the popup script at the same path, so replacing app.wegive.com with portal.wegive.com in the script URL is supported too. Donors following your updated links and embeds will now reach Portal V2. Any links you leave on app.wegive.com, including links in previously sent emails, will continue taking donors to V1. After updating your links, test them from your actual website and messages. Monitor donations, sign-ins, analytics, and donor feedback to confirm everything looks right.

​
Return to V1 if needed

Change your donor-facing links and embeds back from portal.wegive.com to app.wegive.com, preserving the rest of each address. Test your website buttons, embedded forms, and popups again. This sends donors using those updated entry points back to V1. Links already distributed with the V2 address will still point to V2.

​
Path B: Your organization uses a custom domain

​
Create a testing domain

  1. In the admin dashboard, navigate to Settings → Installation.
  2. Add a separate domain for testing, such as my.custom-domain-test.org.
  3. Set that domain to target Portal V2.
  4. Complete the domain setup instructions, including any required DNS and certificate setup. Ask the person who manages your domain to help if needed.
  5. Keep your existing live domain pointed to Portal V1 while you test.
Once the testing domain is ready, visit it to review Portal V2. Your organization identifier is optional on a V2 custom domain. For example, both https://my.custom-domain-test.org and https://my.custom-domain-test.org/my-org-slug work. Existing links containing your organization identifier do not need to be rewritten.

​
Preview and test Portal V2

At your testing domain, review your theme and portal settings, and complete the pre-launch testing checklist below. Test thoroughly before changing the live domain. If you assign a theme specifically to the testing domain, make sure the live domain will use the intended theme too. A theme assigned only to the testing domain does not automatically become the live domain’s theme. Verify your analytics during testing. Confirm that visits, completed donations, and campaign attribution appear as expected, accounting for any tracking rules that exclude your testing domain.

​
Switch your live domain to Portal V2

When testing is complete and you are ready to launch:
  1. Return to Settings → Installation.
  2. Find your live custom domain, which currently targets Portal V1.
  3. Change its target to Portal V2.
  4. Confirm the change.
Within 60 seconds, your custom domain will begin routing donor traffic to Portal V2. If a donor’s browser has V1 cached, it may take longer for that donor to see V2. Your custom-domain links and embeds keep the same address, so you do not need to replace them to switch portal versions. Existing links that include your organization identifier continue to work. If you also publish links on app.wegive.com, update those separately using Path A. Repeat the switch for any other live custom domains you want to move to V2. Visit the live domain and test your website buttons, embeds, sign-in, and donation flow. Recheck analytics and any enabled payment wallets on the live domain, since domain-specific behavior may differ from your testing domain. Monitor donations and donor feedback after launch.

​
Return to V1 if needed

In Settings → Installation, change the live domain’s target back to Portal V1 and confirm. Allow 60 seconds for routing to update. Browser caching may delay when some donors see the change. If you switched more than one domain, switch each one back as needed. Recheck your live links and embeds after the change.

​
Pre-launch testing checklist

Use this checklist on your V2 preview address or testing domain before moving donor traffic. Focus on the features your organization uses.
  • Appearance — Check your logo, colors, fonts, favicon, and page layouts on desktop and mobile. Review both light and dark modes if available.
  • Navigation and settings — Confirm menu items, custom links, your default donation page, and donor-facing features appear as intended.
  • Existing redirects — Try representative redirected links and confirm they reach the expected destination. Your existing redirects carry over; you do not need to recreate them.
  • Donor access and data — Sign in with an existing donor account. Confirm profile information, giving history, tax documents, and saved payment methods appear as expected.
  • Donations — Test the donation flows and payment methods you offer, including donation confirmation and receipts.
  • Recurring giving and pledges — Confirm existing records are visible and that the management options you offer work as expected.
  • Website embeds and popups — Test them in the website context donors will use, including on mobile.
  • Analytics — Verify page visits, donation conversions, and attribution in the analytics tools your organization uses.
Resolve any issues with WeGive before launching. After cutover, repeat the key checks at your live donor entry points and monitor the experience.
Last modified on October 7, 2026