All work · Media & entertainment
Decades of Billboard chart data moved off SQL Server 7, Classic ASP and Visual FoxPro onto Azure, while the books the business sells kept getting published.
A music-chart publisher's entire archive lived on SQL Server 7, a Classic ASP application and Visual FoxPro book-generation tools: a stack nobody could hire for, on hardware that would not last. The business ran on it every day, so it could not be taken down to be replaced.
Restored the old backups into Azure SQL, rebuilt the application for the cloud with proper user and admin security, and kept the FoxPro book-generation tools running against the new database throughout, so publishing never stopped. Built a data validator that pulls chart data from an outside source, converts it to the publisher's own conventions, and shows an editor exactly what will be written before anything goes to production. Used an LLM to reverse-engineer legacy records with a confidence score on each, and statistical sampling to verify rather than trust.
Live on Azure. Along the way the validator found that weeks-at-peak figures in the published data had been silently inflated for years, a data error nobody knew they had.
Stack
Tell me what it does for the business, what it is written in, and what stops when it goes down. I will say plainly whether I can help.
Tell me what it runs on