Accessing legacy project
My client failed to inform me about the migration last year, and by October when their site went down, we'd missed the migration deadline.
At that time, I was still able to see their old site in the editor. I recreated the home page then but was too busy to deal with the rest of it.
Now I can't even open the old site at all in my dashboard; it just pulls an error. How can I access my old content so I can see what was there to recreate it?
(The site was https://www.ascensionlutheranchurch.ca/)
-
Hi Pamela,
Thank you for contacting us.
If the original website is no longer accessible through the editor, one option is to check whether archived copies of the site are available through the Internet Archive's Wayback Machine:
To check for archived versions:
1. Visit the Wayback Machine website.
2. Enter your client's domain name in the search box.
3. Select one of the available snapshot dates from before the site went offline.
4. Browse through the archived pages to view the site's content and layout.
5. Use those archived pages as a reference to recreate the website in Brizy.Please note that the Wayback Machine may not have captured every page or media file, but it can often be a helpful resource when rebuilding a site that is no longer accessible.
If you have any furter questions, please let us know.
Kind regards,
Ariel H.0 -
I should have started by noting that I started with that, but the Wayback Machine is missing quite a few images and some pages altogether.
I see a few comments on here from others who are disappointed not to be able to download their legacy sites; I add my disappointment to theirs.
0 -
Hi Pamela,
Thank you for the update. We understand the disappointment. We gave notice about legacy cloud projects in June 2025, and we also extended access through October to give people additional time to retrieve what they needed. Unfortunately, after that extended window closed, legacy project downloads are no longer available from our side.
0
Please sign in to leave a comment.
Comments
3 comments