Move from SAP Engagement Cloud (formerly SAP Emarsys) to Bento.

Export your SAP Engagement Cloud (formerly SAP Emarsys) data, bring it into Bento, and rebuild what matters while SAP Engagement Cloud (formerly SAP Emarsys) keeps sending. Cancel only when Bento is ready.

Start free trialPlan your switch
Import from SAP Engagement Cloud (formerly SAP Emarsys)Complex migration
CSVemarsys-contacts.csv12,400 rows, mapped
  • SubscribersImports directly
  • TagsImports directly
  • Custom fieldsImports directly
  • AutomationsRebuild in Bento
  • TemplatesPartly moves
  • Commerce dataPartly moves
  • Email historyPartly moves
3 of 7kinds of data import directly
  • Laravel News
  • Examine
  • Less Annoying CRM
  • Geocodio
  • Authority Hacker
  • HeadshotPro
  • QuickMail
4.8/5 on G25/5 on Capterra
SOC 2 Type II, zero exceptions(opens in a new tab)

SAP Engagement Cloud (formerly SAP Emarsys) to Bento, at a glance.

From Bento's SAP Engagement Cloud (formerly SAP Emarsys) migration guide. Still deciding? Read Bento vs SAP Engagement Cloud (formerly SAP Emarsys).

Complex

Migration difficulty

Varies by contact volume, programs, channels, integrations, and reporting scope.

3 of 7

Kinds of data that import directly

The rest you rebuild in Bento or leave behind.

6

Export steps in SAP Engagement Cloud (formerly SAP Emarsys)

Each one is written out below, with tips.

Your time depends on list size and how many flows you rebuild.

Four steps off SAP Engagement Cloud (formerly SAP Emarsys).

SAP Engagement Cloud (formerly SAP Emarsys) keeps sending the whole time. You cancel only after Bento carries your mail.

  1. Export from SAP Engagement Cloud (formerly SAP Emarsys).

    6 steps in SAP Engagement Cloud (formerly SAP Emarsys), in the order below. Nothing changes for your subscribers yet.

    Export from SAP Engagement Cloud (formerly SAP Emarsys)6 steps
    1. 1Review your current Emarsys setupAudit your contact database, key segments, automations, and transactional flows so you know what needs to move first.
    2. 2Export contacts and custom fieldsUse the Emarsys contact export tools to download all contacts as CSV files, including custom fields, consent status, and unique identifiers.
    3. 3Export segments and contact listsExport the members of important contact lists and segments into separate CSV files so you can recreate them as tags and segments in Bento.
    4. 4Export suppression and opt out dataExport unsubscribed, bounced, and blocked contacts from Emarsys so you can mark them as non emailable in Bento.
    5. 5Document automations and programsFor each active automation program, record triggers, delays, filters, and messages so you can rebuild the flow using Bento workflows and sequences.
    6. 6Export email templates and assetsDownload email HTML, layout snippets, and images from Emarsys so you can recreate or adapt them in Bento's editors.
    Keep SAP Engagement Cloud (formerly SAP Emarsys) sending while you export.

  2. Import into Bento.

    Upload the CSV and map each column to a Bento field or tag. Suppressions go in first, so nobody who left gets mail.

    PeopleImportsemarsys-contacts.csv

    Start import
    CSV columnBento fieldType
    • emailEmailIdentity
    • first_nameFirst nameField
    • last_nameLast nameField
    • tagsTagsTags
    • planplanCustom field
    • last_order_atlast_order_atCustom field

    Rows

    12,400

    Before sending

    • Suppressions imported first
    • Unsubscribes kept unsubscribed
    • Tags created from the tags column

  3. Test, then switch.

    Authenticate your sending domain, rebuild the flow that earns the most, and send a seed test while SAP Engagement Cloud (formerly SAP Emarsys) keeps sending.

    Launch checklist4 of 5
    • Sending domain authenticated in Bento
    • Suppressions moved from SAP Engagement Cloud (formerly SAP Emarsys)
    • Seed test sent and checked
    • Highest-revenue flow rebuilt and tested
    • Switch sending to BentoNext
    Warm up with your most engaged subscribers first.

  4. Cancel SAP Engagement Cloud (formerly SAP Emarsys) last.

    Warm up with your most engaged subscribers, move the rest of your sending, and cancel SAP Engagement Cloud (formerly SAP Emarsys) only once Bento carries it.

    Sending, by phase
    PhaseSAP Engagement Cloud (formerly SAP Emarsys)Bento
    1. ExportSendingNot yet
    2. ImportSendingImporting
    3. Rebuild and testSendingTesting
    4. Warm upSendingWarming
    5. Cancel SAP Engagement Cloud (formerly SAP Emarsys)OffSending
    No gap in sending at any phase.

Export your SAP Engagement Cloud (formerly SAP Emarsys) data.

Run these in SAP Engagement Cloud (formerly SAP Emarsys) before you change anything there. Keep the files somewhere safe until Bento is sending.

  1. 1

    Review your current Emarsys setup

    Audit your contact database, key segments, automations, and transactional flows so you know what needs to move first.

    TipList high value programs such as welcome, post purchase, and winback so you can rebuild them early in Bento.

  2. 2

    Export contacts and custom fields

    Use the Emarsys contact export tools to download all contacts as CSV files, including custom fields, consent status, and unique identifiers.

    TipInclude a stable customer ID or email in every export so you can safely de duplicate data in Bento.

  3. 3

    Export segments and contact lists

    Export the members of important contact lists and segments into separate CSV files so you can recreate them as tags and segments in Bento.

    TipName export files after the list or segment in Emarsys to keep mapping simple during import.

  4. 4

    Export suppression and opt out data

    Export unsubscribed, bounced, and blocked contacts from Emarsys so you can mark them as non emailable in Bento.

    TipImport suppression lists into Bento before sending any production campaigns.

  5. 5

    Document automations and programs

    For each active automation program, record triggers, delays, filters, and messages so you can rebuild the flow using Bento workflows and sequences.

    TipScreenshots or exports of each step make it easier to recreate logic without missing key conditions.

  6. 6

    Export email templates and assets

    Download email HTML, layout snippets, and images from Emarsys so you can recreate or adapt them in Bento's editors.

    TipStart with your highest traffic campaigns and transactional templates before lower volume messages.

What comes with you.

3 of 7 kinds of data import directly. The rest you rebuild in Bento or leave behind.

Your import checklist

Import from SAP Engagement Cloud (formerly SAP Emarsys)3 of 7 direct
  • SubscribersImports directly
  • TagsImports directly
  • Custom fieldsImports directly
  • AutomationsRebuild in Bento
  • TemplatesPartly moves
  • Commerce dataPartly moves
  • Email historyPartly moves

Same ideas, new names

SAP Engagement Cloud (formerly SAP Emarsys)Bento
  • ContactPersonA single customer or subscriber identified by an email address or ID.
  • Contact ListTag/SegmentStatic or saved groups of contacts that you can represent with tags and dynamic segments in Bento.
  • Automation ProgramWorkflow/SequenceAn automated journey that sends messages based on triggers and rules.
  • TacticPrebuilt WorkflowA preconfigured strategy that you can mirror with Bento's templates and workflows.
  • Predictive SegmentSegmentA group built from behavior and attributes that you can recreate with Bento segment rules.
  • EventEventA tracked action such as a page view, add to cart, or order that you can send into Bento for targeting.
  • Relational DataCustom Fields and EventsExtra data about customers, orders, and products that you attach as fields or events in Bento.

Before you cancel SAP Engagement Cloud (formerly SAP Emarsys)

  • Prioritise the programs that drive the most revenue and rebuild those first in Bento.
  • Keep Emarsys running during a short overlap period while you test Bento flows with smaller segments.
  • Use consistent naming for tags, segments, and fields so teams can recognise familiar concepts.
  • Plan a dry run with internal email addresses before pointing production DNS records at Bento.
  • Work with your development team to send key ecommerce events like orders and refunds into Bento early in the migration.
  • Automation programs and predictive models do not export directly, so budget time to rebuild them in Bento.
  • Do not cancel your Emarsys contract or update DNS records until you have verified live sends from Bento.
  • Large contact databases can take time to export and import, so schedule migration windows outside of peak campaign periods.

Get a person to plan the move.

Tell us your current provider, list size, and what you need to keep. We map the order to move things and review your domain setup before you send.

Plan your switchGet a migration quote

A migration request

you@example.comMigration quote

We are on SAP Engagement Cloud (formerly SAP Emarsys) with 12,400 contacts. We need to keep subscribers, tags, and suppressions.

Bento teamReplied

Thanks. Start with suppressions, then your list, then the flows that make money. We can review your domain setup before you send.

Teams switch for deliverability and stay for the support.

“Moving to Bento was the best thing I ever did for my list and its profitability”
Iliane L.G2
“I love how easy it is to use to design SaaS emailing sequences. You can also see rapidly which campaigns are the money makers. But what I love the most is undoubtedly the deliverability that you have once you've set up custom domain tracking”
Arnaud B.G2
“The support and community within Bento is hands down the best I've ever seen from any company, ever.”
Luke J.G2

Questions about leaving SAP Engagement Cloud (formerly SAP Emarsys).

Will I lose my Emarsys data and automation programs when I switch?
Your contacts, custom fields, segments, and suppression lists export as CSV and import into Bento. Automation programs need to be rebuilt, but this is a chance to simplify complex journeys. Historical engagement data stays in Emarsys for reference.
How difficult is it to migrate from Emarsys to Bento?
The timeline depends on contact volume, active programs, channels, integrations, templates, domains, and reporting needs. Contacts, fields, and key segments can move through exports, while automations need to be rebuilt and tested in controlled phases.
Will switching hurt my email deliverability?
No provider can guarantee inbox placement after a switch. SAP Engagement Cloud and Bento both support sender authentication. Bento includes reputation monitoring, authentication setup, list hygiene, and sending controls. Preserve suppressions, warm with engaged recipients, and monitor bounces and complaints.
Will there be downtime?
No. Keep SAP Engagement Cloud (formerly SAP Emarsys) running while you import, test, authenticate your sending domain, and warm up. Once Bento is ready, move your sending and phase out SAP Engagement Cloud (formerly SAP Emarsys).
Can the Bento team help if I get stuck?
Yes. The team can review your current setup, help you decide what to move first, and advise on deliverability, data mapping, and launch order.

Other migration guides.

From KlaviyoMedium migrationFrom ActiveCampaignMedium migrationFrom HubSpotComplex migrationFrom OmnisendMedium migrationFrom Customer.ioMedium migrationAll migration guides

Start your move from SAP Engagement Cloud (formerly SAP Emarsys).

Free for 30 days. We help you move your lists, flows, and templates.

Start free trialBook a demo