Legacy Platform to Zoho: A Structured Transformation
A legacy platform was slowing the studio down. I ran a 40-week, evidence-led migration to Zoho that cut platform costs by 60% with zero downtime.
Why we had to act
Our project management system was no longer serving the evolving needs of our teams. It slowed us down, frustrated users, and lacked the adaptability modern teams demand. The mission: design and deliver a tool that helps teams collaborate smarter, work faster, and lead with clarity.
I'm not always clear on what to work on or prioritise.
Design Team, User Sentiment SurveyFeedback like this, alongside comments such as "the dashboard gives no clear visibility" and "we end up avoiding the old platform for real collaboration", made the case for change concrete rather than theoretical.
Six interconnected gaps
Before proposing any changes, I ran structured interviews across the team. The friction wasn't isolated to one system complaint. It spanned six linked areas:
A 40-week, evidence-led transformation
- Weeks 1–3, Preparation: Identified core challenges with the legacy platform, defined success criteria, aligned leadership on goals.
- Weeks 4–9, Vendor Research: Shortlisted Monday.com, Zoho, Microsoft Planner, and ClickUp; narrowed to Monday.com and Zoho after internal feedback and needs assessment.
- Weeks 10–19, Pilot & Evaluation: A cross-functional pilot group, made up of Account Management, Project Management, Design, and Finance, ran hands-on demos and testing, scored on usability, reporting, automation, and scalability.
- Weeks 20–40, Customisation & Go-Live: 4–5 months configuring Zoho Projects, CRM, and Books to match real workflows, with role-based dashboards and automation.
Zoho was selected through a collaborative, KPI-driven evaluation with real user input. It wasn't a top-down decision.
"Say Hello to Zoho": the internal campaign
A platform switch fails or succeeds on adoption, not configuration. Starting one week before launch, I ran a structured, week-by-week communication campaign:
- Week 1, Awareness: "Zoho is coming!" This shared why the change was happening and what to expect.
- Week 2, Education & Engagement: Tool capabilities, early benefits, testimonials from the pilot group.
- Week 3, Training & Support: Role-specific training sessions, SharePoint hub with tutorials and guides.
- Week 4, Launch Plan: Confirmed launch date, plus a final checklist covering logins, sessions, and who to contact for help.
Training was tailored by function. Project Managers, Account Managers, Designers, and Finance each had customised sessions, supported by detailed user manuals, FAQs, and step-by-step video tutorials. During launch week, Zoho representatives were onsite for real-time support, and the Operations team tracked every reported blocker for fast escalation and resolution.
To manage the risk of migrating legacy data, I chose a controlled overlap strategy: ongoing and critical projects were closed out on the legacy platform, while new projects started fresh in Zoho. This minimised data loss without an all-at-once cutover.
Results
Platform costs were reduced by 60%, while the new platform provided more capabilities than the previous system. The migration ran with full operational continuity: zero downtime and zero data loss, plus a 7.8 out of 10 adoption satisfaction score, with user complaints reduced significantly compared to the legacy system. The transition also recorded the highest invoicing value the studio had seen, reflecting better-governed projects and a healthier delivery pipeline.
