Why Every Import Starts With an Automatic Backup
Imports are among the most powerful features in our platform. With one workflow, an organization can bring in a whole website, thousands of members, years of blog posts or an entire product catalog. That power is exactly why imports deserve caution. An import can write more data in a few minutes than a person could enter in a year, and if something goes wrong, it can be just as hard to undo.
So every import in our platform begins the same way: with a full backup of the account, prepared and verified automatically, before a single record is written.
Why a reminder is not enough
Many systems handle this with a friendly warning: "We recommend backing up before importing." Some add a link to a backups page. In practice, people in the middle of a big task rarely stop to make a backup, and a backup that someone meant to make protects nobody.
We decided the backup should not depend on anyone remembering. The import workflow prepares the backup itself, waits for it, verifies it and only then lets the import continue. There is no setting to skip it and no shortcut that leads around it.
What counts as a real recovery point
Not every file called "backup" is a recovery point. Ours must meet three conditions before an import is allowed to proceed:
- It finished. The backup operation completed rather than stopping partway.
- It passed verification. The archive was checked for integrity after it was written.
- Its files still exist. The backup artifacts are present, either locally or at a usable remote destination.
A backup that is pending, interrupted, empty or only queued is not protection, and we never describe it as if it were. You can read more about that standard in a backup is not a backup until it is verified.
The workflow keeps moving on its own
An automatic backup could easily become an annoying wait. We designed the step so it stays out of the way. The import screen shows the backup's progress, and when verification passes, the workflow advances on its own to the import. If the backup fails, the person sees a clear explanation and can retry right there, without leaving the import or starting over.
Rechecking before the first write
Time passes between preparing a backup and writing the first imported record. In that gap, things can change. So before the import writes anything, it rechecks that the backup belongs to the same account, is recent enough to be meaningful and that its files are still intact. Only then does it proceed.
This recheck happens on the server, in the same code that does the importing, not just on the screen. A person cannot bypass it by reloading the page or calling the import directly.
Imports still keep their other safeguards
The backup is the safety net, not the only safeguard. Imports also show a review of what was found in the source before anything is written, ask for a final confirmation, respect the account's plan and keep data within the right website. Some data, such as payment history, is never imported in ways that could recreate charges. The backup protects against the unexpected; the review protects against the expected mistakes.
Restores are a separate, careful decision
Having a backup does not mean restores happen casually. Restoring an account replaces current data, which can also lose work done after the backup. Restores require an explicit decision by an authorized person and a fresh snapshot of the current state first, so even a restore can be undone.
A small delay for a lot of peace of mind
The automatic backup adds a few minutes to an import. In exchange, the organization knows that if the import surprises them, there is a known good state to return to. That trade is easy to make when the data belongs to someone else. It is part of the same care that shapes how we rehearse a website migration and everything in VoVo.
Frequently asked questions
Do I need to make a backup before importing into VoVo?
No. VoVo prepares and verifies a full backup of your account automatically before any import writes data.
What happens if the automatic backup fails?
The import does not continue. You see what went wrong and can retry the backup from the same screen.
Can a backup be used to undo an import?
A verified backup is a recovery point that can be restored by an authorized person. Restores are handled carefully because they replace current data.
Related Posts
Why Every Change We Ship Goes Through One Pipeline
We never deploy by logging into a server and running commands. Every change travels through the same automated pipeline. Here is why that discipline matters.
Every Payment Lands in the Books
A payment that never reaches the accounting records creates work and risk later. Here is how our payment flows connect to the books from the very first charge.
One-Time Content Seeders That Respect Later Edits
When we publish pages, settings or articles for a website through code, the change runs once, checks its assumptions and never overwrites what the owner changes afterward.
Keeping AI Model Choices Current
AI models change every few months, and yesterday's best choice can quietly become outdated. Here is how we keep model choices current without breaking features.
Designing AI Features That Refuse to Invent Facts
AI models are confident even when they are wrong. Here is how we design AI features to work from approved sources, admit gaps and hand off to people instead of improvising.
Comments (0)
No comments yet. Be the first to share your thoughts!