How long does migration to Sesamy take?

Typical migration timeline is 2–4 weeks from first data handoff to go-live. Multi-brand publishers migrate one publication at a time to reduce risk. Single-brand cases usually land at the faster end of the range. The timeline depends on source-system complexity more than headcount, so we quote after reviewing your data.

Will existing subscribers need to re-enter payment details?

No. Sesamy handles payment token portability including Vipps account takeover, Stripe PAN import, and Klarna / Kustom account continuity. Existing subscribers keep paying without interruption on the same rails they already use. The handover is invisible from the subscriber side — no forced re-authorisation, no new signup flow.

What systems can Sesamy migrate from?

Sesamy has migrated 80+ publishers from Infosoft, Flowy, and custom-built legacy systems with zero downtime. The process is data-shape agnostic — if you can export subscriber, product, and billing data in any tabular format, our data team handles the schema translation into Sesamy.

Is there a Sesamy alternative to Infosoft?

Yes. Sesamy has migrated publishers from Infosoft with zero downtime. The platform handles print fulfilment, digital subscriptions, and B2B billing in one system with modern self-service tools — including Vipps, Swish, OCR/KID, and direct integrations with Helthjem and DI for Nordic print distribution.

Migration

Switching platforms does not have to mean losing subscribers.

80+ publishers have migrated to Sesamy from Infosoft, Flowy, and custom-built legacy systems: with zero downtime and payment continuity for existing subscribers. Whether they pay by Vipps, Stripe, or Klarna.

Talk to our migration team See the five-step process

The honest answer

We know why you have not switched yet.

Every publisher evaluating a new platform has the same two fears. Will the migration break something? And will existing subscribers still be able to pay?

These are legitimate concerns. Migrations always have unknowns. We do not pretend otherwise. What we bring is a process built from 80+ migrations, a dedicated data team involved in every single one, and the experience to identify and resolve issues before data enters the live system.

When issues surface post-launch, and some always do, we handle them together. This is a process we work through, not a guarantee we hand you on a slide.

The process

Five steps. Honest about what happens at each.

Typical timeline is 2–4 weeks from first data handoff to go-live. Multi-brand publishers migrate one publication at a time.

01
Data handoff
You export subscriber data from your current system. We accept exports from Infosoft, Flowy, and custom-built platforms.
Our data team reviews every file before any import begins: subscriber records, product catalogues, billing histories, access entitlements. Messy data is expected, not a blocker. We handle the format translation between your current system and Sesamy so your team focuses on the business questions instead of file schemas.
02
Mapping and validation
We map your products, subscriptions, and billing structures to Sesamy, flag discrepancies, and resolve them before go-live.
You get overview PDFs and raw data access to verify everything. Every edge case (lifetime subscribers, frozen accounts, paused renewals, B2B seat pools) is mapped explicitly and signed off. Nothing moves into the live system until you confirm the mapping matches reality.
03
Payment continuity
Existing subscribers keep paying without re-entering card details — Vipps, Stripe, and Klarna all covered.
Vipps account takeover transfers agreements without re-authorisation. Stripe PAN import moves card tokens securely. Klarna and Kustom accounts stay live. This is the part publishers worry about most and the part we have the most receipts on — every one of the 80+ migrations has cleared this gate.
04
Go-live
One publication at a time. Let it settle. Validate. Then proceed with the next.
This is more cautious than a big-bang migration, but it is how you avoid surprises. Most multi-brand publishers are fully live in 2–4 weeks from first handoff; single-brand cases usually land at the faster end. You set the pace — we do not force a cutover timeline that does not fit your editorial calendar.
05
Post-launch support
Some issues only surface after real traffic hits the platform. We expect this.
Our team monitors the first days and weeks, resolves issues as they appear, and works with your team until everything is stable. There is no arbitrary support-handoff date — we stay engaged until your team says the migration is done.

Payment continuity

Your existing subscribers keep paying. No interruption.

The question that kills more migration deals than feature gaps. Here is how each of the three mechanisms we own actually works.

Vipps continuity mechanism: Existing Vipps subscription agreements transfer to Sesamy without requiring re-authorisation from the subscriber. The agreement continues on the same renewal cadence, on the same payment rail, with no "confirm your subscription" interstitial to kill conversion.
Stripe continuity mechanism: Card details migrate securely using the Stripe PCI-compliant card import process so recurring charges continue uninterrupted. Customers keep their own Stripe account — Sesamy is not the processor of record, which means migration is also reversible.
Klarna / Kustom continuity mechanism: Existing Klarna and Kustom payment agreements are preserved in the handover. Subscribers paying through invoice or Klarna instalments stay on the same plan with the same terms. No new signup, no broken billing cycle.

The result: your subscribers do not notice the switch. They keep reading. They keep paying. They keep being your subscribers.

Track record

80+ publishers. Zero downtime.

0
Publisher migrations: Zero
Downtime during migration: 2–4 weeks
Typical timeline

Migrated from: Infosoft, Flowy, and custom-built legacy systems.

What makes this different

A dedicated data team on every migration.

We do not hand you a CSV template and wish you luck. Every migration has a dedicated data team involved from first data handoff through post-launch. They know the quirks of legacy systems. They know where data gets messy. They catch issues before they reach your subscribers.

This is not a self-service migration tool. It is a process we work through together.

Common questions

What publishers ask before signing.

How long does migration to Sesamy take?: Typical migration timeline is 2–4 weeks from first data handoff to go-live. Multi-brand publishers migrate one publication at a time to reduce risk. Single-brand cases usually land at the faster end of the range. The timeline depends on source-system complexity more than headcount, so we quote after reviewing your data.
Will existing subscribers need to re-enter payment details?: No. Sesamy handles payment token portability including Vipps account takeover, Stripe PAN import, and Klarna / Kustom account continuity. Existing subscribers keep paying without interruption on the same rails they already use. The handover is invisible from the subscriber side — no forced re-authorisation, no new signup flow.
What systems can Sesamy migrate from?: Sesamy has migrated 80+ publishers from Infosoft, Flowy, and custom-built legacy systems with zero downtime. The process is data-shape agnostic — if you can export subscriber, product, and billing data in any tabular format, our data team handles the schema translation into Sesamy.
Is there a Sesamy alternative to Infosoft?: Yes. Sesamy has migrated publishers from Infosoft with zero downtime. The platform handles print fulfilment, digital subscriptions, and B2B billing in one system with modern self-service tools — including Vipps, Swish, OCR/KID, and direct integrations with Helthjem and DI for Nordic print distribution.

Ready to talk about your migration?

Tell us what system you are on and we will walk you through how the switch works. Data shape, payment continuity, timeline.

Talk to our migration team Or see the platform