Kevel migration

Migrate from Kevel
toTopsort.

Translate your existing retail media setup into commerce-native infrastructure with a migration process built around mapping, validation, and controlled review.

From Kevel
Into Topsort
Advertiser
Vendor
Flight
Campaign
Ad
Bid
Creative
Asset
Zone / placement
Slot
/The migration model

We move your setup over —without copying the old system line by line.

Kevel and Topsort are structured differently. So migration is not a literal copy-paste.

Instead, we take the parts of your existing retail media program that matter — like advertisers, campaigns, placements, and creatives — and rebuild them in Topsort in the right way.

What you already have in Kevel
  • Advertisers
  • Campaigns
  • Placements
  • Creatives
  • Delivery rules
What Topsort does during migration
  • Understands how each part is being used
  • Rebuilds it in the right Topsort structure
  • Flags anything that needs review
What you get in Topsort
  • Vendors
  • Campaigns
  • Assets
  • Slots
  • Validated setup

The goal is simple: preserve how your media business works, while moving it into a structure built for commerce.

/How it works

From source snapshot to validated campaigns.

Kevel source structureTopsort structure
01

Export

Create a structured snapshot of the existing environment.

AdvertisersCampaignsFlightsInventoryCreativesTargeting
Kevel
Advertisers
Flights
Zones
Topsort
Snapshot

The migration guide starts by exporting the Kevel campaign and inventory tree so later steps work from a consistent source snapshot.

  1. Create a structured snapshot of the existing environment.

    AdvertisersCampaignsFlightsInventoryCreativesTargeting
    Advertisers, Flights, ZonesSnapshot

    The migration guide starts by exporting the Kevel campaign and inventory tree so later steps work from a consistent source snapshot.

/Commerce-specific migration

Product ads aren’t just another ad placement.

For Sponsored Listings, the migration has to understand the catalog, not just inventory placement.

01

Identify the products

Existing product identifiers are matched against the commerce catalog.

02

Validate the selection

Fixed SKU selections can be translated into explicit product targets.

03

Separate product logic from placement logic

Sponsored Listings are treated as catalog-driven commerce ads rather than simply inheriting generic display-placement structure.

Your catalog becomes part of the migration —not an afterthought.

/Migration control

Know what happened to every campaign.

migration-report
Source
Topsort
Migration status
Review
Flight 9012
Campaign A
✓ Migrated
Flight 9013
Campaign B
↻ Translated
Delivery model adjusted
Flight 9020
Campaign C
! Review
Product selection

Every migrated unit can retain its source identity, destination identity, status, and review notes — making it easier to validate the transition before retiring the old system.

/Before go-live

Migration isn’t done when the objects exist.

Campaign structure

Did dates, budgets, formats, and advertiser relationships translate correctly?

Inventory

Are campaigns serving in the intended placements?

Creative

Are assets associated with the right campaigns and formats?

Product selection

Are Sponsored Listings connected to valid catalog products?

Delivery controls

Are targeting, frequency, and scheduling behaviors operating as intended?

Reporting

Can teams trace campaigns and events consistently across the transition?

/After migration

A cleaner foundation — with the migration history intact.

Traceable

Know where each source campaign ended up.

Reviewable

Surface differences instead of hiding them.

Commerce-aware

Treat products and catalog relationships as first-class migration inputs.

Automatable

Designed for automation, so repetitive translation and validation can be handled programmatically.

/Next step

Planning a move from Kevel?

Start by mapping what should move directly, what should be translated, and what deserves a closer look before cutover.