What can’t be restored automatically
- Contact forms — the visual layout may be recoverable, but form submission requires a backend to process and deliver the data
- User login and account systems — authentication depends on a live database of user records, which the archive never stored
- Site search — search indexes are built and queried server-side; the archive only captures individual result pages
- E-commerce carts and checkout — product listings may appear in snapshots, but cart state, inventory, and payment processing all require a live backend
Why the archive can’t help here
Archive snapshots do not include:- Databases — user accounts, orders, product catalogues, and any other stored records
- Server-side scripts — PHP, Python, Ruby, Node.js, or any other code that ran on your server
- API connections — integrations with payment processors, CRMs, email platforms, or other external services
Options for getting dynamic features back
Static form layouts (visual only)
Static form layouts (visual only)
We can restore the visual appearance of your forms — labels, fields, and buttons — as static HTML. The layout will look correct, but submissions won’t be processed until you connect a form backend. Third-party services such as Formspree, Netlify Forms, or similar can be added to a static HTML site to handle submissions without a custom backend.
WordPress plugins for replacement features
WordPress plugins for replacement features
If you choose the WordPress delivery format, many common dynamic features are available as plugins. Contact forms (e.g., WPForms, Contact Form 7), site search (e.g., SearchWP), and basic e-commerce (e.g., WooCommerce) can be set up after restoration without custom development.
Custom redevelopment
Custom redevelopment
For features that require a bespoke solution — membership systems, booking engines, custom APIs — we offer custom development as a separate service. Contact us with your requirements to discuss scope and pricing.

