NoCodeBackend

Product details
waterandmolddamagerestorationwaterandmolddamagerestoration
waterandmolddamagerestoration
Sep 16, 2026

Q: Moving data between Databases

Can data be moved between databases without breaking relationships, IDs, and history?

Is it possible to upgrade from one LTD plan to another later while retaining existing data and features?

What happens if a database reaches the record limit? Does it become read-only, or are only new records blocked?

Is there a rate limit on how many records can be read or written per request?

Thanks,

Founder Team
Riya_NoCodeBackend

Riya_NoCodeBackend

Sep 17, 2026

A: Hello,

1. Moving Data Between Databases:
Yes. You can use our built-in Snapshots (1-click backup & restore) or export full SQL dumps from the dashboard. Because these use native database dumps, all auto-increment IDs, primary keys, foreign key relationships, timestamps, and history remain 100% intact.

2. Upgrading LTD Plans:
Yes, as long as our deal is live on AppSumo. You can upgrade directly in AppSumo at any time while the campaign is active. Once our campaign concludes and leaves AppSumo, tier upgrades will no longer be possible.

3. Reaching Record Limits:
Only new record insertions (POST) are blocked. The database does not become frozen or read-only:
Reads (GET), Updates (PUT/PATCH), and Deletions (DELETE) continue working 100% normally.
Only new row insertions are rejected with an HTTP 403 limit message until you upgrade or delete older records.
You will also receive an automated email alert when a database hits its limit.

4. Record Limits Per Request:
Reads (GET): You can fetch up to 1,000 records per request using pagination. You can paginate through larger datasets using _offset.
Writes (POST): You can insert single rows or batch arrays. For bulk writes, you can insert up to 500 records at once in a single API call.

Please let us know if you need anything else!

Share
Helpful?
0
Log in to join the conversation
Related questions
View product details