Migration guide · updated 13 mai 2026
Switching comment systems is two weeks of work.
Whether you run Disqus, Viafoura, OpenWeb, Coral, Opinary or an in-house build, the migration to Logora follows the same playbook. Two to eight weeks, zero comment loss, zero SEO loss, no double login. The plan below is the one we ran at Der Spiegel, Milenio and Krone.
The five-step playbook
From first call to old vendor decommissioned.
-
Day 0
01
60-min call with a co-founder
Pierre or Henry walk through your current vendor setup, your reader account model, your moderation policy, your DSA exposure. We come back within 48 hours with a scoped migration plan.
-
Day 3-5
02
Account opened on a gated audience
We open a Logora workspace and deploy on a controlled subscriber circle (500-5,000 readers, typically tied to one newsletter). ~2 hours on your tech team for the JS snippet + OAuth client config. Old vendor stays untouched.
-
Day 7-14
03
Historical comments imported
Through the vendor's export API (Disqus, Viafoura, Coral) or via your archived database. We map accounts, dates, threads, votes. Same operation we ran at Spiegel and Milenio: zero comment loss.
-
Day 14-30
04
SSO bridged, paywall hooked
Single sign-on with your existing reader account system goes live. Subscriber tier respected. Reader graph stays in your database. Old vendor decommissioning planned.
-
Day 30-60
05
Editorial onboarding + first live debates
Newsroom team trained on prompt-building, moderation admin, journalist avatar workflow. Old vendor switched to read-only or fully shut down. Decision call with measurable data on retention, moderation load, engagement.
Four worries we kill on day one
What you don't have to worry about.
-
Zero comment loss
We import the full history: accounts, comments, replies, votes, timestamps. Same import we ran at Spiegel (Twitter/Facebook archives) and Milenio (Facebook Comments).
-
Zero SEO loss
URLs preserved. Microdata Comment schema preserved. canonical links and structured data align with your existing setup.
-
No double login
SSO bridged to your existing IdP from day one. Subscribers comment in one click. No reader has to recreate an account.
-
Reader graph stays yours
Logora is your data processor under Article 28 GDPR. The reader accounts live in your database. Migration consolidates first-party data, doesn't leak it.
Multi-platform moderation
Comments aggregated from your website + social properties
- Websitelogora.com · 1 247 todaylive
- Facebook page@logora · 412 todaylive
- YouTube@logora · 289 todaylive
- Instagram@logora · 178 todaylive
One moderation pipeline, four platforms, same editorial standard.
Which vendor are you leaving?
The specifics per vendor.
Each comment platform has its own export quirks. The high-level playbook is the same; the implementation details differ. Pick yours, we'll send the specific migration brief.
-
Coming from
Disqus
Export, snippet + SSO bridge, then the reader graph is yours. Schrems II liability dropped on day one.
See the migration guide -
Coming from
Viafoura
Comment + account export. Newsroom-first workflow replaces ad-tech-driven engagement plays.
See the comparison -
Coming from
OpenWeb
Drop the all-or-nothing platform. Keep the modules you need (comments, debates, consultations).
See the comparison -
Coming from
Coral (Vox)
From OSS-you-operate to operated-and-supported. ML moderation included by default.
See the comparison -
Coming from
Netino
Keep Netino for social media if you want, Logora handles on-domain debates and comments.
See the comparison -
Coming from
Opinary
Add the conversation layer on top of polls. Two systems coexist on the same articles.
See the comparison -
Coming from
Facebook Comments
Pattern Milenio: +150% comments year 1, +100% year 2 after the switch. Audience stays on your domain.
See the migration guide -
Coming from
In-house build
Build vs buy, side by side: time-to-live, total cost and the maintenance that compounds after launch.
See the comparison
Migration questions
What publishers actually ask.
-
How long does a vendor switch actually take?
Two to eight weeks depending on your auth stack, your archive size, and your newsroom training timeline. Milenio replaced Facebook Comments in two weeks. Larger archives (~5M comments) take ~6 weeks.
-
What happens to comments older than 5 years?
Imported by default. We anonymise on request (most regions allow up to 5-10 years of editorial archive retention). Per-comment legal review is included for sensitive content.
-
Will we keep our reader account IDs?
Yes. Logora references your accounts by ID, we don't reissue them. Subscribers don't notice the switch from their side, except that comments load faster and the debate format appears.
-
What about the moderation team that was working in the old vendor's admin?
They get a new admin with keyboard shortcuts (3× faster after the Feb 2026 release). Training is part of the migration package, typically 2 hours of live walkthrough plus async docs.
-
Can we run Logora alongside the old vendor for a few weeks?
Yes, that's the default pattern. Logora handles the new content; the old vendor stays in read-only on the historical archive. After 4-8 weeks of parallel running, you decommission.
-
Is there a migration fee?
Typically no, for switches at scale. We absorb the migration work as part of the first-year subscription. For smaller deployments, a fixed migration package may apply, discussed during the 60-min call.
Bring us your current setup, we bring back a migration plan.
A 60-min call with Pierre or Henry. Tell us your current vendor, your auth stack, your archive size. You leave with a scoped plan, a timeline, and a number. Most pilots start free for the first month.