Drupal to WordPress for UK Charities: Plan Donations, Events and Editor Handover
A migration brief for UK charities that need to preserve useful content and donation journeys while making the replacement website manageable for editors.
In this article
Illustrative workspace. Screens show concepts, not a delivered client system.
A UK charity’s website may combine resources, events, campaign pages and donation links maintained by a small staff or volunteer team. Moving Drupal to WordPress should preserve the journeys the organisation relies on while giving those editors a practical publishing model.
My Drupal to WordPress migration service is offered remotely from India as an assessed rebuild and content-transfer scope. This guide focuses on charity publishing and operational boundaries, rather than assuming a website migration also replaces every donor or fundraising system.
Inventory content by its role in the organisation
List resources, news, event pages, campaigns and contact routes. Record which pages are current, which are useful historical material and which should be retired with an appropriate destination. A page count alone does not reveal the structure of the content or the people who maintain it.
Include downloads and externally shared links. An older report may still be referenced by a partner, even if it is not featured on the homepage. Identify important URLs and decide whether to retain them or map them to suitable replacements.
- Content types and representative pages.
- Linked files, categories and related content.
- Campaign and donation destinations.
- Staff or volunteer owners for review.
Map relationships as well as text
Drupal’s JSON:API core concepts distinguishes attributes from relationships between resources. Where that access is available and suitable, it can provide source material; the WordPress destination still needs its own mapping and templates.
Check how an event relates to a venue, how resources use categories and whether one content item appears in several listings. Flattening everything into independent page text can make later publishing harder. The extraction method depends on the Drupal version, modules and authorised source access.
Agree a representative transfer sample before importing the entire inventory. Compare content values, media references and the links that connect the items.
Keep the donation journey and its provider boundary visible
Record the path a visitor follows to donate: a link, an embedded form or a hosted provider page. Identify who owns the fundraising account and which connected records or notifications the website actually influences. A visual rebuild should not silently alter a working payment journey.
Donor records, fundraising settings and finance decisions need separate owners and scope. The organisation supplies the approved donation wording and operational rules. The website project implements the agreed public-facing path; it should not be presented as a substitute for the charity’s fundraising administration.
| Journey | Migration check |
|---|---|
| Campaign page to donation provider | The intended destination and campaign context remain correct |
| Embedded donation interface | The supported embed behaves in the replacement layout |
| Confirmation page | The approved next step and links remain coherent |
| Connected reporting | The owner reviews the agreed attribution requirements |
Design templates for the people who will edit them
Ask the future editors to show their ordinary tasks: publishing an event, replacing a download or updating campaign information. Use that exercise to choose structured fields, reusable sections and templates. A team with occasional volunteer editors benefits from clear controls and a short handover.
For an Elementor implementation, specify native widgets and shared site parts. Review optional fields, long titles and mobile layouts. Decide which global content needs a central owner and which pages can be maintained independently.
Use approved content for launch. Sample campaign pages or fictional records can support a demonstration when labelled, but they should not become invented public evidence of fundraising work.
Plan a release around live campaigns and content changes
Agree the content cut-off and the handling of edits made during the rebuild. A charity may have an active campaign or scheduled event that cannot simply disappear while the replacement is prepared. Record any deadline and the people required to approve the relevant journey.
- Important URLs and the approved redirect map.
- Representative resources, events and donation routes.
- Editor permissions and routine publishing checks.
- Internal links, search metadata and sitemap entries.
- Release, recovery and post-release review responsibilities.
The website project should identify the checks it can perform and those belonging to an external provider. Use authorised test arrangements where notifications or transactions need review.
Separate the migration from additional functionality
Does moving to WordPress mean replacing the donor CRM? No. Keeping an existing supported system can be a separate decision. Define that architecture before commissioning the transfer.
Can we add events or membership features? Assess the actual requirement, available plugins and custom work. Those features need their own data and operating decisions, rather than being hidden inside a page migration estimate.
Will search rankings remain identical? A migration can preserve useful URLs and apply a reviewed launch plan, but it cannot promise unchanged positions. The migration overview explains the broader discovery and release process.
Prepare a charity migration brief
Share the public Drupal website, version if known, content inventory and priority journeys. Include fundraising-provider boundaries, downloads, active campaigns and the editors who will maintain the replacement. Describe access constraints without sending donor exports through a public quote form.
I can assess that brief and scope a WordPress and Elementor rebuild, representative transfer and editor handover for your UK charity. Discuss your charity website migration to agree the dependencies and the first reviewable sample.
Written by
Jagjeet Singh
Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.
Explore my work
