Bringing a 2008 community site back to life

The problem

Swinging Bird launched in 2000 as a hand-built ASP and Access site and peaked at 3,500 visitors a day. By 2014 it had been shut down, riddled with SQL injection and impossible to patch.

In 2026 an old backup drive turned out to be readable again: two decades of forum threads, articles, polls, species pages and member records, all in a schema nobody had touched since 2008. The question was whether it could come back as a real, maintained product rather than a static archive.

What we built

• Scripts that parse the legacy ASP exports into Postgres on Supabase: forum topics and replies, exchange listings, polls and votes, illness threads, photo albums and member profiles
• Photos on Cloudflare R2, with every import scripted so it can be re-run and verified against the source
• Original accounts kept as unclaimed records: members sign in with their old password and are upgraded to a modern account with email verification
• One users table reached through an expand, backfill and contract migration, so old authors stay linked to their original posts
• Site-wide full-text search, @mentions and notifications, a species directory and encyclopedia, and a newsletter
• An AI assistant that answers bird-care questions using only the site's own articles and links
• A Next.js, React and Tailwind frontend deployed on Netlify

Screenshots

The result

• Content and member records recovered from a 2008 ASP and Access backup
• Original members can claim their old accounts with their old password
• 130+ articles, 70 species profiles, forum, polls, photo albums and chat
• Built and maintained by one person working with AI coding agents