Migrating from Orchard to GiftAider
GiftAider migrates Orchard data into GiftAider Breeze by importing directly from the charity’s Microsoft Access database, usually the full Orchard .mdb file. We do not ask your charity to rebuild donor, donation and Gift Aid history by hand.
A practical route from Orchard to Breeze
This migration is for charities moving their Gift Aid processing from Orchard into GiftAider Breeze. The work starts with the Access database itself, so we can import from the real source data, run setup tests, check the results in a sandbox, and agree what is ready before the site goes live.
We keep the language careful and practical: Orchard databases can differ from charity to charity, so the right first step is a controlled Access database import and sandbox review, not a promise that every field will map automatically.
What we normally ask for
- The full Orchard .mdb Microsoft Access database.
- Any notes about how your team currently records Gift Aid.
- Recent claim totals or reports for comparison.
- A contact who understands your donor and donation data.
How the Orchard migration works
1. Secure Access database handover
You provide the Orchard .mdb Microsoft Access database so we can work from the complete source, not a partial spreadsheet export.
2. Direct import and setup tests
We import from the Access database into a controlled GiftAider Breeze setup, then run setup tests against donor, donation and claim-related data. Declaration evidence is checked in the source data before upload.
3. Mapping checks
Useful fields are checked and mapped into Breeze so donor and donation records stay meaningful. Declarations are not managed inside Breeze.
4. Sandbox presentation
We present the imported data in a sandbox so your team can review records, totals and practical workflows before anything goes live.
5. Validation and fixes
GiftAider checks for issues such as missing postcodes, duplicate donors and unclear claim status, so these can be reviewed before go-live.
6. Go-live readiness
Once the sandbox has been reviewed and setup tests are passed, we agree the go-live plan and prepare your first claim in Breeze.
What can be brought across?
| Data area | What we check | Why it matters |
|---|---|---|
| Donors | Names, addresses, postcodes, donor references and duplicates. | Clean donor records support accurate Gift Aid claims. |
| Donations | Dates, amounts, source references and historic claim state. | GiftAider needs reliable donation history before claims are prepared. |
| Declarations | Declaration dates, status and available source evidence. | Declarations help decide whether donations are claimable. |
| Reports and totals | Recent totals from Orchard compared with sandbox import outputs. | This gives your team a practical check before go-live. |
Why this is Breeze, not Amplify
Orchard migration is positioned here as a route into GiftAider Breeze, the Standard Gift Aid submission product. If your charity also needs CRM configuration, custom attributes or required fields, that is a separate Amplify conversation.
Frequently asked questions
Do you need a CSV export from Orchard?
No. For Orchard migration we expect to work directly from the full Orchard .mdb Microsoft Access database so the data can be imported and tested properly.
Will every Access database field be imported?
Not automatically. We review the Access database and agree which fields should become Breeze records, notes or reference data.
Can we review the import before going live?
Yes. We present the imported data in a sandbox and compare key donor, donation and claim figures before first-claim work begins.