Sometimes a restore is exactly the right move - and sometimes it wipes out days of work or puts a hack straight back. Which one it is depends on what went wrong, when, and what the backup actually contains.
When a restore is the right call
If a plugin or theme update broke the site and you know exactly when it happened, restoring to the backup taken just before that update is usually the fastest, safest fix. Same goes for a bad content edit or a configuration change you can't undo - the backup is a time machine, and going back is often cheaper than moving forward.
When it isn't
If your site was hacked a while ago, every backup you have may already contain the malware - restoring just re-infects the site. If orders, form submissions, or posts were added since the backup, a restore deletes them permanently. And if the backup is months old, you're choosing to lose all the work in between.
The questions to ask first
- What caused the problem, and when? If you can't answer that, you don't know what you're restoring away from..
- Is the backup clean? On a hacked site, that's not guaranteed..
- What will I lose between the backup and now? Orders, leads, and posts are easy to forget..
How we handle it
We look at the site first, work out what actually happened, and only restore when it's the right tool. Where a restore loses recent work, we separate the content from the fix so you keep both. It's part of looking before we quote.
Rather just have it handled?
Site Down or Critical Error Fix
From $180, flat rate. You approve the price before we start.