What a 90-Day CMS Migration Teaches ABM Landing Pages
As of November 2026, if you are shortlisting a partner for ai seo singapore, the question is no longer whether a CMS migration can happen inside one quarter, but what you keep and who owns the recovery afterwards.
SoftServe is the case to study for that. The global AI and technology services firm, an Optimizely partner since 2016, moved its full website onto Optimizely One in 90 days while launching a rebrand at the same time. Later, the same team turned account-page production into something that runs in minutes, and that second half matters more to a lead-generation team in Singapore than the migration story itself.
I have sat in on enough replatform meetings to recognise the pattern. The marketing team signs off on the new site in a conference room, someone says "SEO will be fine, we kept the redirects", and four months later the organic enquiry form goes quiet while the team blames the algorithm. The SoftServe story is useful because it shows both halves in one place: a migration done under a hard deadline, then a landing page engine that only works because the platform underneath it is healthy.
Key takeaways
- The 90-day figure describes one company's website build, planning included; SoftServe says its build took 60 days and the rest went on preparation.
- Content, not the template, is the part that outlives the deadline: over a thousand content items moved across after launch.
- ABM page production at SoftServe fell from hand-built pages for a dozen accounts to a target of 500.
- For a Singapore B2B team, the SEO partner's job after go-live is index recovery and ranking monitoring, not the migration project itself.
What actually took 90 days
Heather Bain, Head of DXP and MarTech Strategy at SoftServe, describes her CMO asking for a full website migration and a rebrand within a quarter, and calling the request unheard of. The team signed the contract on Christmas Eve and had the new site live by the end of the first quarter. The build itself took 60 days; the rest of the calendar went on planning.
That split is the first lesson, and it is the one most teams skip. Before anything was removed, business analysts, project managers and internal tiger teams worked through each module, and SoftServe's partner team planned alongside the internal digital and web group. Bain's own summary of the trap is blunt: lifting a broken instance into a new platform leaves you with a broken instance on better hardware.
If you are choosing between best seo singapore firms on the strength of a migration promise, ask what happens in weeks one and two. A migration that puts 60 days into building and zero into an old-site URL inventory is a migration that will discover its broken pages in month two, when the traffic has already dropped.
I have watched a content team at a professional services firm learn this the hard way. Their new site went live on a Thursday, the redirects covered the top-level pages only, and by the following Tuesday the enquiry form was collecting about a fifth of the traffic it had the week before. Nobody had done anything wrong in the build. They had simply left the URL inventory to whoever had time, which in practice meant nobody.
The part nobody budgets for: content
The new site went live, and the content was a different problem. Bain admits the team took on more than it could chew by migrating decades of content while rebranding, and her advice to anyone in the same position is to cut unnecessary content first.
What carried the load was automation with a human checkpoint. The partner team built agents that ran the migration in five stages, from discover and classify through extract, transform and enrich, deploy and QA, and anything unusual went to a person for review. One agent moved blog posts from a live URL straight into a draft in the new CMS. Since launch, over a thousand content items have moved across.
For a Singapore SME running a site with a few hundred service pages, the ratio is smaller but the mechanism is the same: classify first, automate the repetitive extraction, and keep a person on the pages that carry commercial value. The failure mode is not the volume, it is migrating everything without deciding which pages were worth keeping.
Why page production fell from weeks to hours
On the old stack, publishing content meant checks, manual coding, front-end and back-end work, and it took weeks or months to get something live. After the move, page production time fell 85-93%, and building a page went from around five days to three to six hours, with no code changes needed for new page types.
Heather Bain puts the business reason in one line: a campaign that takes three months to build is a campaign about what was happening three months ago. In the AI and IT services market she works in, content can go stale inside three months, which makes a slow publishing pipeline a resource leak rather than a delay.
SoftServe's own account of a 60-day DXP migration makes the same point from the other direction, citing publishing time cut to three to six hours and every page template implemented. Two documents from the same company, one describing the client project and one describing the vendor-side migration, land on the same range.
From a dozen hand-built accounts to 500
The ABM piece is where lead generation teams will pay closest attention. The ABM team used to build account pages in HubSpot by hand, each one through weeks of approvals, and that limited them to a dozen or so champion accounts out of the 2,500 the team should have been targeting. Personalisation covered fifteen accounts; the team is now working towards a target of 500.
The mechanism is not a faster builder alone. Adam Seabridge and his team built a pipeline of 14 agents that score and rank accounts on tech stack, digital maturity, financials, leadership changes, market sentiment and answer-engine and generative-engine visibility. Once a week, a workflow agent checks for updated account data and triggers an agent that builds the page, and a person can review any page before it goes live.
Read that last sentence carefully, because it is where a buyer should push. The review step still exists; the team says it rarely needs it now. That is a claim about their data quality and their templates, not a claim that a firm with thin account data can switch the human off on day one.
The rehearsal rule for account pages
Here is the concept I would put in front of any Singapore team planning ABM pages: rehearse on ten accounts before you scale to a hundred. SoftServe's own advice from Bain is to start with the data you already have, perhaps the CRM, then add signals from sales platforms or market data as you go. The pipeline was stood up in days rather than months, and it still needed the human review step to carry it in the first weeks.
For a small team, ten accounts is enough to surface the problems you would otherwise find at a hundred: missing firmographic fields, a template that breaks on long company names, and sales colleagues asking why the page exists at all.
The rehearsal gives you four checks before volume: does the CRM hold the segments the agents need, do the templates survive real account data, does a person still catch errors at a reasonable rate, and does the page actually reach sales?
| Stage | What the team builds by hand | What the agents take over | Human checkpoint |
|---|---|---|---|
| Account selection | Manually picking champion accounts | Scoring and ranking 2,500 accounts weekly | Review the top-tier list |
| Page assembly | Weeks of approvals per page | Draft built from account data | Sample review before publish |
| Copy | Written per account | Assembled from known account facts | Sign-off on regulated claims |
| Tracking | Added per campaign | Wired into the template once | Check the first batch in analytics |
What a CMS migration breaks, and who owns the fix
Migration projects carry a predictable set of SEO injuries, and most of them are not visible on launch day:
To make this concrete, here are the injuries I see most often, in the order they tend to bite:
- Old URLs that no longer resolve and lose their rankings before a redirect exists.
- A redirect map that was built from the sitemap rather than from actual traffic data.
- New templates that drop the title and H-tag rules the old pages followed.
- A robots.txt or staging rule left in place so the new site is quietly blocked from crawling.
- Internal links pointing at pages that were merged or deleted.
- Sitemaps that list the old structure and never get resubmitted.
None of this is a reason to avoid a CMS migration; SoftServe proved the build can be fast. It is a reason to contract the recovery phase explicitly, because the person who built the site and the person who watches the index are rarely the same person.
How Topkee pulls the two timelines apart
This is where Topkee's own descriptions are worth reading before you brief anyone on an SEO engagement. The company publishes a first-90-days rhythm for its ai seo singapore work: the first fortnight confirms goals, permissions and the keyword and question set, and fixes the baseline; the second half of the first month clears priority issues and checks that the first content is published; months two and three improve topics and pages, then review delivery, visibility, visits and query quality. The material labels this an implementation rhythm, not a ranking deadline, and it is a recommended arrangement rather than an external commitment.
That distinction matters for a migration. Topkee's SEO audit treats website migration analysis as one item on a technical checklist, alongside robots.txt availability, page redirects, missing-page and server errors, sitemaps, HTTPS, structured headings and responsive testing. So migration continuity in that framing has three points: a pre-launch baseline of the old site's URLs and rankings, a cutover with redirects, missing-page handling and link fixes, and a post-launch phase that re-crawls and re-indexes titles and metadata and reports ranking change and index status. None of it is a 90-day migration project, and no honest SEO partner should sell one.
The same point of view applies to the second half of the SoftServe story. Topkee does not sell an ABM product, so treat an account-page matrix as a method suggestion, not a promise. What does back it up is the WEBER Web Builder, a drag-and-drop builder usable without a designer or a developer, with over a hundred industry templates, global settings that change every element sharing an attribute in one action, shared modules reusable across an account, multilingual pages and built-in title, URL, H-tag and alt field settings. Paid tiers start at a low monthly price after a free trial. Combined with the high-performance landing page deployment service, which puts speed, clarity and tracking on the same page, that is the machinery behind fast production of paid-traffic pages.
For a Singapore team, the two timelines should be written on the same page and kept apart: the IT build has a date, and the SEO recovery has a rhythm that starts before the build and outlasts it.
If you need a second opinion on which of those three points your current site would fail, Topkee runs a diagnostic covering more than twenty metrics, from load speed and mobile compatibility to backlink quality, with an instant recommendation report and scheduled re-checks rather than a one-off acceptance test.
What I would watch next quarter
Three things decide whether a fast migration turns into faster lead generation, and none of them shows up in a launch announcement.
The first is index recovery in the month after launch. A site that launches in January and shows its ranking recovery in the monthly position report by March is on track; one that shows a flat or falling line needs the technical audit rerun rather than more content.
The second is who reviews account pages once volume arrives, and where the handover is written down in the contract with the best seo singapore partner. SoftServe's reviewers say they rarely need to intervene now, and that is the number to watch in your own team: the share of generated pages that get rejected at review. If it climbs, the account data is thin and the templates are guessing.
The third is whether the slow part moved. If migration compressed publishing from weeks to hours, the bottleneck shifts to approval, legal review and campaign planning. Teams that do not notice that shift end up with a fast website and a slow marketing calendar.
FAQ
Can a full website migration really be done in 90 days?
Yes, with qualifications. SoftServe moved its full website onto Optimizely One in 90 days while launching a rebrand, but the build itself took 60 days and the rest went on planning each module before anything was replaced. The content migration continued after launch, with more than 1,000 content items moved across since.
What does a CMS migration break in SEO terms?
The usual damage is lost URLs without redirects, a redirect map built from the sitemap instead of traffic data, new templates that drop title and heading rules, a robots or staging rule left blocking the new site, broken internal links, an outdated sitemap. Each item has a fix, but only if someone owns it before launch.
How many accounts can an ABM team personalise?
At SoftServe, hand-built pages in HubSpot limited the team to a dozen or so champion accounts out of the 2,500 it should target. A pipeline of 14 scoring agents and a page-building agent moved it from personalising for fifteen accounts to a target of 500, with a person able to review each page.
Should a Singapore company hire an SEO agency before or after the migration?
Before. A pre-migration baseline of old URLs, rankings and index status is the only way to tell later whether a drop came from the migration or from the market. An agency that joins after go-live can still do redirect work and index recovery, but it loses the comparison.
Is the Topkee 90-day rhythm a migration timetable?
No. Topkee's material describes 90 days as an SEO implementation rhythm, from a baseline in the first fortnight to a review in month three, and states it is not a ranking deadline. CMS migration appears as one item on its technical audit checklist, so the SEO work can align to that rhythm while the site build runs to the IT team's own schedule.
Recommended next step
If a replatform is on your calendar, start with the audit rather than the build brief. Topkee's ai seo singapore service sets out the keyword, page and tracking work that follows a launch, and the custom AI agent development service is where the agent-and-review pattern from this case shows up on the engineering side. If your team is also running paid campaigns, the AI-optimised PMax case for nonprofit sponsorship growth is a useful read on how landing page changes and paid traffic interact.
Sources
- Heather Bain and Adam Seabridge, "SoftServe: 90-day CMS migration and 2-minute ABM pages", Optimizely field notes, 2026-11-05. https://www.optimizely.com/field-notes/customer-stories/softserve
- "See Our Own 60-Day DXP Migration", SoftServe, no published date. https://info.softserveinc.com/see-our-own-60-day-dxp-migration
