Moving to Bloomreach.
New to Bloomreach or moving from another tool: what moves, what breaks, and a plan around your deadline. We start within a week, and a co-founder leads the move. 10 years on Bloomreach, since it was Exponea.
Your old tool
In Bloomreach
Profiles
Keyed on one ID
Consent
Opt-in dates kept
Event history
Original timestamps
Product catalog
Fed new from the shop
Email templates
Rebuilt as a system
Campaigns
Rebuilt, not copied
Six things to carry over. Each has one trap.
Profiles
File or API, keyed on email or your customer ID. Watch: choose the ID before the first import.
Consent
Imported as consent events. Watch: keep the original date, or you can’t prove when people opted in.
Event history
Imported with the original timestamp. Watch: old events can start live flows. Guard them first.
Product catalog
New catalog fed from the shop. Watch: every schema change reprocesses the whole catalog. Decide the fields once.
Email templates
Rebuilt or imported as HTML. Watch: plan a template system first.
Campaigns
Segments, flows and scenarios are rebuilt in Bloomreach, not copied. Watch: export the old reports before access ends.
The six usual mistakes.
Old events start live flows.
A three-year purchase import can send a thank-you to everyone. Guard every live flow first.
Consent gets the wrong date.
Without the original timestamp, every consent gets the upload date.
The catalog is created too early.
Every later schema change reprocesses the whole catalog and can break the campaigns that use it.
Templates are treated as a copy job.
Build shared rows, styles and one master per language first.
Two tools paid for too long.
The move slips and the old contract renews.
Full volume on day one.
A new sending domain needs 2 to 4 weeks of warm-up, or the mail lands in spam.
Moving from another tool? About 10 to 16 weeks, planned back from your deadline.
01
Week 1: data definitions. Which events, attributes and objects move, and which don’t.
02
Week 2: identification. One customer ID, tracking and consent in place, profiles merged right.
03
Weeks 3 to 4: objects and data migration. Profiles, consent and events with original dates. The catalog is fed new from the shop.
04
Weeks 5 to 6: reintegrating. Shop, app, CRM and data sources connected to Bloomreach.
05
Weeks 7 to 8: rebuilding. Templates, segments and flows, the ones that earn most first. Each flow gets its guard before it goes live.
06
Weeks 8 to 11: email warm-up. New sending domain warmed up while both tools run. Two to four weeks, depending on volume.
07
Weeks 10 to 16: switch off. Once your full volume runs on Bloomreach: old tool read-only, reports exported, API keys revoked, a written map handed over.
Renewal sooner than that? We launch the three flows that earn most first.
New to Bloomreach? About 10 weeks.
01
Week 1: data definitions. Which events, attributes and IDs you need.
02
Weeks 2 to 3: data imports. Real-time tracking and history.
03
Weeks 4 to 6: channels and sources. Email, SMS, push, web, app, ad audiences, your shop and CRM.
04
Weeks 7 to 9: first use cases. Picked by customer stage, from first visit to repeat purchase.
05
Week 10: results and handover. What works, what comes next, a written map of what feeds what.
Rado and Jan, the co-founders.
One of us leads your project, start to finish. Behind us, senior consultants in Slovakia, Czechia, Slovenia and Portugal.
Questions teams ask before we start.
Tell us what you need.
Bring your renewal date. We reply by email within one business day.

