Enterprise Database Modernization
Libercus, E. Viddal & Associates' newspaper publishing platform, supported multiple newspaper organizations across North America. As the customer base expanded, the existing Microsoft SQL Server architecture created increasing licensing costs, infrastructure complexity, and limitations on future scalability.
I led the product strategy and cross-functional coordination for a platform-wide migration from Microsoft SQL Server to MySQL, partnering with engineering teams, infrastructure specialists, QA, and customer stakeholders to modernize the platform while minimizing operational risk across every customer implementation.
CLIENT
E. Viddal & Associates
PRODUCT
Libercus Publishing Platform
Role
Director of Product Development
Service
Enterprise Platform Modernization
The Challenge
By 2018, Libercus had evolved into a shared publishing platform powering 21 newspaper publications across five independent media organizations. Supporting multiple customers on a common platform increased the importance of scalability, reliability, and operational efficiency.
The existing Microsoft SQL Server architecture had become increasingly costly to operate and constrained future platform growth. Rather than executing a simple database migration, we led a strategic modernization initiative to transition the platform to MySQL—reducing licensing costs, simplifying infrastructure, and establishing a scalable foundation for future product innovation.
Key Challenges
Rising Microsoft SQL Server licensing costs increased operating expenses across every customer deployment.
Multiple newspaper implementations required careful planning to avoid disrupting active publishing operations.
Millions of production records had to be migrated with zero data loss and minimal downtime.
Hundreds of application queries and integrations required modernization for MySQL compatibility.
Cross-functional coordination was required across engineering, QA, infrastructure, product, and the Libercus vendor.
The rollout needed to preserve business continuity while creating a scalable foundation for future platform growth.
Business Objectives
The database modernization initiative was designed to achieve several strategic business outcomes that extended beyond replacing the underlying database technology. The focus was on reducing operational costs, improving platform scalability, and creating a stronger foundation for future product innovation across every customer deployment.
Primary Objectives
Reduce enterprise infrastructure costs by eliminating Microsoft SQL Server licensing across customer deployments.
Simplify platform architecture by standardizing on an open-source database platform.
Improve scalability to support additional newspaper organizations without increasing platform complexity.
Reduce operational risk through a phased migration strategy with comprehensive testing and rollout planning.
Accelerate future product development by modernizing the underlying platform architecture.
Improve deployment consistency across all customer environments.
Create a foundation for future modernization initiatives, including cloud infrastructure, performance optimization, and new product capabilities.
Improve customer experience by increasing platform stability, reliability, and long-term maintainability.
Product Strategy
Rather than treating the effort as a one-time database replacement, we developed a phased platform modernization strategy that balanced technical risk, business continuity, and long-term scalability.
The roadmap was organized into coordinated workstreams that progressed in parallel, allowing development, testing, and infrastructure planning to advance simultaneously while reducing implementation risk.
Development environment modernization
Database schema conversion
Application code refactoring
Query modernization
ETL migration development
Quality Assurance & Integration Testing
Customer User Acceptance Testing (UAT)
High Availability & Disaster Recovery Planning
This phased delivery model reduced implementation risk by validating each workstream before production deployment, ensuring a stable migration across multiple customer environments.
Key Roadmap Highlights
Sequenced workstreams to minimize operational risk while supporting active newspaper operations.
Coordinated engineering, infrastructure, QA, product management, and Libercus vendor deliverables.
Validated each migration phase through internal QA followed by customer-specific UAT.
Executed staggered customer deployments to reduce rollout risk and quickly incorporate lessons learned.
Established a repeatable rollout framework used across 21 newspaper publications spanning five media organizations.
Cross-Functional Execution
Successful delivery required close collaboration across engineering, infrastructure, product management, QA, customer support, and the Libercus engineering team. Because the platform served multiple newspaper organizations simultaneously, every technical decision had to balance customer requirements, release timelines, and operational stability.
Throughout the project, I led cross-functional planning sessions, coordinated issue triage, prioritized customer-specific requirements, managed release readiness reviews, and aligned deployment activities across internal teams and external vendors to ensure each rollout remained on schedule.
Major execution workstreams included:
SQL Server to MySQL database migration
Database schema conversion and validation
Application query modernization
ETL migration development
Customer-specific implementation updates
QA and Customer UAT coordination
High Availability and Disaster Recovery planning
Production deployment and rollout coordination
This coordinated delivery approach enabled multiple technical workstreams to progress in parallel while reducing deployment risk and minimizing disruption across 21 newspaper publications.
Key Product Decisions
Throughout the modernization initiative, I made several strategic product decisions that balanced customer impact, technical complexity, implementation risk, and long-term platform goals. These decisions reduced rollout risk while creating a scalable foundation for future enhancements.
🚀 Phased Customer Rollout
01
Released customers in staged waves rather than a single enterprise cutover, reducing deployment risk while incorporating lessons learned into each subsequent rollout.
⚙️ Parallel Workstreams
03
Organized engineering, QA, infrastructure, and product activities to run in parallel whenever possible, shortening the overall project timeline.
📰 Shared Platform Architecture
05
Maintained a common enterprise platform while accommodating customer-specific configurations across 21 newspaper publications.
✅ Customer UAT Before Production
02
Required every newspaper to complete dedicated User Acceptance Testing before production deployment, ensuring customer-specific workflows were fully validated.
🛡️ High Availability & DR
04
Included HA and disaster recovery planning as part of the migration strategy rather than treating resilience as a post-launch activity.
🗄️ SQL → MySQL Migration
06
Treated the database migration as a broader platform modernization initiative focused on scalability, flexibility, and long-term cost reduction.
Business Impact
The SQL Server to MySQL modernization established a scalable foundation that enabled the Libercus platform to continue growing while reducing long-term operational costs. Beyond the technical migration, the initiative improved deployment flexibility, simplified infrastructure management, and created a modern architecture capable of supporting additional newspaper organizations and future product enhancements.
Lessons Learned
Enterprise modernization projects are as much about leadership and execution as they are about technology. This initiative reinforced several principles that continue to shape how I approach product management today.
My Role
As Product Manager, I owned the strategy, planning, and cross-functional delivery of the enterprise database modernization initiative, aligning engineering, infrastructure, QA, and customer stakeholders while balancing business priorities, technical complexity, and release risk across 21 newspaper publications.
Core Leadership Responsibilities
• Product strategy & roadmap
• Engineering prioritization
• Customer requirements
• Implementation planning
• Cross-functional leadership
• Enterprise platform strategy
• Release planning
• User Acceptance Testing
• Production deployments
• Risk management
• Stakeholder communication
• Issue prioritization
Scope of Ownership
21 newspaper publications
5 phased customer rollouts
Enterprise platform modernization
End-to-end product lifecycle
What This Project Demonstrates
This project reflects the type of product leadership I bring to enterprise software organizations: translating complex technical initiatives into customer-focused product strategies, aligning cross-functional teams, and delivering scalable solutions that create long-term business value.
From roadmap planning and stakeholder alignment to phased deployments and customer adoption, this project highlights my ability to lead enterprise modernization efforts while balancing delivery risk, platform evolution, and customer success.