
Clockify's Time Doctor Migration Video: Naming the Enemy on Purpose
Clockify published a named-competitor migration tutorial for Time Doctor users. Detected on its landing page, the move targets switching-cost friction directly.
Jordan Reeves
Founder & Operator · · Updated
TL;DR
- Detected 75% rarity, 70% importance CRO pattern on Clockify's landing page.
- Clockify runs a dedicated video tutorial titled "Import data from Time Doctor."
- The tutorial covers migrating clients, tags, team members, and past tracked time.
- Evidence quote: "continue tracking time in the simplest tool possible."
- Category logged: unique_mechanic — a rare page element, not a standard A/B test variant.
- Pattern targets switching-cost friction for a named competitor's existing customers.
What did Clockify actually publish?
Clockify built and published a step-by-step video walking Time Doctor users through exporting their data and importing it directly into Clockify. This isn't a vague "switch and save" banner — it's a named-competitor migration path with a literal how-to. The on-page copy is explicit: "Import data from Time Doctor - Transfer all your past tracked time, clients, tags, and team members to Clockify and continue tracking time in the simplest tool possible."
I've shipped competitor-comparison pages before. They're easy — throw up a table, bold your checkmarks, ship it Friday. What Clockify did is harder and rarer, which is exactly why it logged at 75% rarity in our detection set. Most teams stop at "we're better than X." Almost nobody builds the literal bridge that lets a prospect walk across.
Why does naming the competitor by name matter here?
Naming the specific competitor collapses the buyer's biggest hesitation — the fear that switching means losing historical data. Most SaaS comparison pages talk in generalities. "Switch from your current time tracker" is safe, legally tidy, and forgettable. "Switch from Time Doctor" is a decision a real prospect is actually googling at 11pm because their team is annoyed with their current tool. Clockify is meeting demand that already exists in search intent and internal Slack complaints, not manufacturing it.
This matters because switching cost isn't really about price — it's about the sunk data. Clients, tags, historical time logs, team member mappings. That's the stuff that makes a founder say "ugh, we'd have to redo all of that" and stay put out of inertia. Landing page CRO guidance from Gomage makes the point that a page should stay focused on one goal and match the message to where the visitor is actually coming from. A Time Doctor user isn't coming from a generic search — they're coming from frustration with a specific product. Clockify's page matches that intent exactly instead of making them translate their problem into generic marketing language.
Is this actually a CRO play or just content marketing?
It's both, and that's what makes it rare — it functions as content marketing and as a bottom-funnel conversion mechanism in the same asset. A blog post about switching tools drives top-of-funnel traffic. A migration tutorial embedded on the landing page does that and then removes the exact objection that kills the conversion at the moment of decision. It's positioned as education, but its job is to get someone from "still on Time Doctor" to "activated on Clockify" without a sales call in between.
Unbounce's CRO framework emphasizes structuring tests around a clear hypothesis — "changing X will improve Y because Z." The implied hypothesis here is straightforward: reducing perceived migration effort will improve trial-to-activation conversion for competitor-switchers, because data loss fear is the primary objection at that stage. Whether Clockify formally tested this or just shipped it on conviction, the logic holds up.
What surfaces did we detect this on, and how common is it?
Migration tutorials naming a specific competitor are still uncommon across the 1,000+ brands we monitor daily, which is why this pattern scored high on rarity.
| Pattern element | Detail |
|---|---|
| Company | Clockify (clockify.me) |
| Surface | Landing page — other |
| Category | unique_mechanic |
| Rarity score | 75% |
| Importance score | 70% |
| Competitor named | Time Doctor |
| Data covered in migration | Tracked time, clients, tags, team members |
Most comparison pages we log fall into predictable buckets: feature tables, pricing call-outs, testimonial swaps. A dedicated named-competitor import walkthrough is a distinct category — it's operational, not persuasive copy. That's the difference between telling someone you're easier to use and proving it by doing the hard part for them.
What would I actually build if I only had one sprint?
If your team is choosing between polishing a comparison page headline and building an actual migration path, build the migration path. Headlines get A/B tested into diminishing returns; friction removal compounds. I've watched a team spend three sprints iterating hero copy on a "switch from X" page while conversion barely moved, because the real blocker was never the words — it was the 40 minutes of manual re-entry a prospect imagined they'd have to do. The fix wasn't better copy. It was a five-minute video and an import script.
Atomix Logistics' CRO guide lists trust elements and clear CTAs as standard levers, but a working import tool is a trust element that doesn't need a testimonial to back it up — it's self-evidently true the moment someone uses it.
Common questions
What is a "unique_mechanic" detection in CRO terms?
It's a page element that functions as a distinct conversion mechanism rather than a copy or layout variant — something with real functionality, like an import tool or calculator, instead of just persuasive text or design changes.
Why would a company name a specific competitor on its own landing page?
Naming a competitor targets high-intent search traffic and internal frustration that already exists, removing the translation step where a visitor has to map generic marketing claims onto their specific switching situation and objection.
Does building a migration tool actually move conversion, or is it just goodwill marketing?
It does both — it captures bottom-funnel switcher intent and removes the sunk-data objection at the exact decision moment, functioning as content marketing and objection-handling simultaneously rather than one or the other.
How rare is this pattern across the brands ABWatcher monitors?
This detection scored 75% rarity, meaning named-competitor migration tutorials remain uncommon compared to standard comparison pages or pricing call-outs across the 1,000+ high-converting brands we track daily.
What should a small team build instead of another headline test?
Pick your one loudest competitor by support-ticket or sales-call mentions and ship a real, working migration path for it this sprint — the friction removal compounds. What I would actually do next: skip the headline test and ship one working migration tool for your single most-mentioned competitor.
Read next
More from the ABWatcher blog
Nov 22, 2026
Snake River Farms Tests a $25-Off Popup on Its Ad Landing Page
We caught Snake River Farms split-testing an email-capture form and $25-off modal on its landing page. Here's the math on what it would take to call a winner.
Nov 21, 2026
Snake River Farms Tests Mid-Page Email Capture on Its Ad Landing Page
SRF is A/B testing a mid-page lead-capture block and a $25-off popup against a simpler hero-only promo banner on its paid landing page, detected 2024 week-over-week.
Nov 20, 2026
Attio Is Testing a New Tier, Higher Prices, and a New Pitch
Attio is running a live pricing page test with a new $1,000 "Ultra" tier, higher Plus/Pro prices, and a new headline — here's what we caught and what it means.
Nov 19, 2026
Found Quietly Tested a 25% Price Cut on Its Pricing Page
We caught Found running a live pricing A/B test with an annual billing toggle that drops Found Plus from $35 to $26.25/mo. Here's what changed and why it matters.
Nov 8, 2026
Astro Proves "Zero Lock-In" With a Live Code Demo, Not a Claim
Astro's homepage replaces a trust badge row with a working, clickable framework demo — here's the hierarchy and interaction design behind it, detected 60% rare on astro.build.
Nov 7, 2026
Basecamp's Big Numbers: Why Hyper-Precise Stats Beat Vague Social Proof
Basecamp's homepage swaps "trusted by thousands" for 1.7 billion to-dos and 5 petabytes of data. We break down why precision beats vagueness as social proof — and how to test it.
From the glossary
Vocabulary the article uses. See all terms →
- Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
- Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
- Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
- Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
- Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
- Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See more like this
ABWatcher catches A/B tests like this across 1,000+ brands.
Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.