---
url: /cashfree-acellemail/backup-and-restore.md
description: >-
  How to protect and restore your Cashfree gateway configuration in AcelleMail —
  there is no built-in backup, so use standard AcelleMail database backups.
---

# Backup and restore

The Cashfree plugin has **no built-in backup system**. Gateway settings and transaction records live
in AcelleMail's core database, so standard AcelleMail backups cover all gateway state.

## What to back up

A standard **AcelleMail database backup** captures all gateway components:

* **Configuration:** License key, App ID, Secret Key, Sandbox toggle, and Webhook Secret.

* **Subscriptions:** Remote plan mappings for the Cashfree Subscription gateway.

* **Transactions:** Invoices, payment logs, and transaction records.

* Keep **regular database backups** on your normal AcelleMail schedule.

* Take a fresh backup **before big changes** — updating the plugin, switching from Sandbox to live, or
  rotating your Cashfree credentials.

::: info Nothing plugin-specific to save
The gateways use AcelleMail's own payment tables and add no custom database tables of their own, so
there's no separate export to keep. A whole-database backup is enough.
:::

## Rolling back

If an update misbehaves, you can roll back:

1. Download the **previous** version ZIP from your relyweb.co client area.
2. Upload it via **Admin → Plugins → Upload Plugin** to overwrite the plugin files.
3. **Restore database only if necessary:** Settings persist across file replacements, so database restoration is only needed if data structures were modified.

After rolling back, confirm the license badge still reads **Active** and that both gateways appear in
**Admin → Payment Gateways**.

## Related pages

* [Updating](/cashfree-acellemail/updating) — how manual updates work
* [Uninstalling](/cashfree-acellemail/uninstalling) — deactivate or remove the plugin
* [Configuration](/cashfree-acellemail/configuration) — re-enter settings if needed
* [Troubleshooting](/cashfree-acellemail/troubleshooting) — recover from a bad update