Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Move Braze to Salesforce Marketing Cloud as a controlled data-and-orchestration migration, not a file transfer. Inventory every campaign, Canvas, segment, event, identity key, and consent state; export source records with their IDs and timestamps; normalize them into Salesforce data extensions and audiences; rebuild messaging in Journey Builder; then run both platforms in parallel until counts, consent, rendering, delivery, and conversions meet agreed thresholds. Keep immutable exports and a rollback plan before activating production sends.
The most important limitation is historical depth. In Braze segment user exports, custom_events, purchases, campaigns_received, and canvases_received contain only the last 90 days. Older history must come from warehouse exports, Currents, Snowflake sharing, data-lake records, or another approved system before Braze is decommissioned.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What does a Braze-to-Salesforce Marketing Cloud migration include?
A complete migration has ten connected workstreams: inventory, extraction, identifier preservation, identity and consent reconciliation, audience rebuild, campaign and journey redesign, event and profile loading, historical-retention recovery, validation, and cutover. Treat each workstream as a controlled release with an owner, evidence, and a rollback action.
- Inventory: catalogue Braze campaigns, Canvases, segments, templates, channels, entry triggers, schedules, control groups, suppression rules, conversion events, custom attributes, custom events, purchases, subscription groups, consent states, and identity keys.
- Extract: collect campaign and Canvas definitions, segment definitions and members, user data, KPIs, sessions, custom events, custom attributes, and purchases.
- Preserve: retain Braze campaign IDs, segment IDs, event names, external IDs, timestamps, source workspace, and export-run metadata.
- Reconcile: choose the authoritative person key, resolve anonymous-to-known profiles, deduplicate, and map every channel’s consent and suppression state.
- Rebuild audiences: create equivalent Salesforce audiences while retaining each original Braze definition beside its target definition.
- Rebuild orchestration: map campaigns and Canvases to Salesforce Marketing Cloud assets, usually in Journey Builder, and label every mapping as equivalent, approximate, or manual redesign.
- Load data: create an event dictionary and import historical profile, event, and purchase data; use the API for ongoing updates where needed.
- Recover history: obtain data older than Braze’s documented 90-day fields from an approved historical source.
- Validate: compare records, audiences, events, consent, rendering, delivery behavior, unsubscribes, conversions, and error queues.
- Cut over: freeze Braze changes, export a final delta, activate Salesforce journeys in waves, monitor production, and retain evidence and rollback instructions.
Do not assume a universal one-to-one conversion table exists. Braze and Salesforce Marketing Cloud differ in data models, trigger semantics, decision logic, frequency controls, and reporting, so each important asset needs an explicit mapping decision.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
How do I inventory the Braze estate before exporting it?
Start with a register that is complete enough for another team to reproduce the current behavior. A campaign name alone is not sufficient: the migration team needs the logic, dependencies, audience, content, and measurement attached to it.
Record campaign and Canvas behavior
- Braze campaign and Canvas IDs, names, tags, status, last-edited time, workspace, channel, and owner.
- Entry trigger or schedule, time zone, eligibility window, re-entry rules, delays, branching conditions, control groups, and frequency caps.
- Message templates, subject lines, localization, personalization fields, fallback values, deep links, and channel-specific settings.
- Suppression lists, quiet hours, subscription-group requirements, global frequency policies, and any exclusion campaign.
- Conversion events, attribution windows, KPI definitions, and the analytics-tracking state at the time each asset ran.
Braze’s campaign-list endpoint exposes campaign name, campaign API identifier, API-campaign status, tags, and last-edited time. Use those fields as a minimum machine-readable inventory and retain the response with the export run: https://braze.com/docs/api/endpoints/export/campaigns/get_campaigns.
Record segments and data dependencies
- Segment name, segment ID or API identifier, tags, filter expression, analytics-tracking status, and representative member samples.
- Every custom attribute, custom event, purchase field, subscription group, and identity field referenced by a filter or message.
- Whether a segment is used as an entry audience, suppression audience, control group, reporting cohort, or ad-hoc export.
- The source and refresh expectation for each field: profile update, event stream, batch import, or manually maintained list.
Classify what should actually move
Separate active production assets from paused, test, one-time, and obsolete assets. Keep obsolete definitions in the archive when they explain historical reporting or consent decisions, but do not recreate them as active Salesforce journeys without an explicit business owner.
How do I export Braze campaigns, segments, users, and events?
Use Braze’s documented export categories and choose API or cloud delivery according to volume, replay needs, and security controls. API responses are JSON. Exports can be delivered through a Braze-managed temporary URL or directly to an organization’s Amazon S3, Azure Blob Storage, or Google Cloud Storage bucket.
Choose the delivery method
| Method | Use it when | Important qualification |
|---|---|---|
| API response | You need repeatable extraction, incremental pulls, or automated retries. | Braze documents that APIs do not have the base 500,000-row CSV limit, but rate and throughput controls still need to be designed and monitored. |
| Braze-managed download URL | You need a quick one-time file transfer. | Without connected cloud storage, Braze says the temporary URL expires after four hours. Download and checksum the file immediately. |
| Customer cloud bucket | You need durable retention, access logging, replay, and handoff to a data pipeline. | Connected S3, Azure Blob Storage, or Google Cloud Storage receives files directly in the customer-controlled bucket. |
| Dashboard CSV | A small analyst export or spot check. | Braze documents a base limit of 500,000 rows for CSV exports; do not use it as the sole path for a larger estate. |
Extract the complete source set
Collect campaign details and analytics, Canvases, segments, user data, KPIs, sessions, custom events, custom attributes, and purchases. Export the definitions as well as the member and activity data: definitions explain how to rebuild behavior, while records allow you to test parity.
- Create an export manifest with asset type, endpoint or job name, request parameters, workspace, start and end time, and expected row or object count.
- Run a small sample and inspect JSON schemas, null behavior, timestamp formats, pagination, and error responses before launching the full extraction.
- Run full exports into immutable storage. Record the request, response metadata, checksum, object path, and operator or service account.
- Repeat exports for deltas during the migration window. Never overwrite an earlier run; timestamp each run and keep the source workspace in the metadata.
- For large data sets, prefer APIs or cloud delivery over a single CSV. Split by date, workspace, object type, or key range when the endpoint supports it.
Do not treat a successful HTTP response as proof of completeness. Reconcile returned counts, pagination cursors, date boundaries, and rejected records, and retain the failed requests for replay.
How do I preserve Braze IDs, timestamps, and a Salesforce crosswalk?
Keep source identifiers as immutable audit fields even when Salesforce uses a different contact key or data-extension primary key. A crosswalk lets you explain a historical Braze send after the cutover and prevents duplicate loading when an export is replayed.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
| Braze source value | Salesforce target representation | Migration rule |
|---|---|---|
| External user ID and anonymous ID | Authoritative ContactKey plus an identity-alias table | Retain every prior identifier, map anonymous-to-known transitions, and mark the surviving key. |
| Campaign ID and Canvas ID | Source-asset fields on a journey or campaign registry | Never regenerate or repurpose the Braze ID; use it for lineage and replay. |
| Segment ID and definition | Audience registry and target segment/data extension | Store the original filter text beside the target filter and its version. |
| Custom event name and properties | Event data extension or event schema | Preserve exact event name, property names, timestamp, source, and retention class. |
| Event, purchase, and campaign timestamps | UTC timestamp fields plus source time-zone metadata when available | Do not convert a timestamp without recording the original value and conversion rule. |
| Export run and source workspace | Load-run audit table | Store extraction time, workspace, file checksum, and processing status. |
Use deterministic matching rules and send ambiguous records to a review queue. A common safe order is an existing consented ContactKey, then a verified external ID, then a deliberately approved email or phone match. Do not use an unverified address as an automatic merge key when multiple profiles can share it.
How do I reconcile identity, consent, and suppression before sending?
Consent is a release gate, not a field to copy after the first Salesforce send. Establish the authoritative person key, resolve anonymous-to-known identities, deduplicate profiles, and reconcile email, SMS, push, subscription-group, opt-in, opt-out, and regional compliance states before any journey is activated.
Build a consent decision table
| Input state | Target action |
|---|---|
| Explicit channel opt-in with a valid ContactKey | Load the consent timestamp, source, region, subscription group, and channel status; allow only the mapped channel. |
| Explicit opt-out or suppression | Load the suppression with its effective timestamp and reason; block sends until a documented re-opt-in process changes it. |
| Conflicting records | Apply the approved precedence rule, preserve both source records, and route the conflict for review. |
| Anonymous profile later matched to a known person | Link the IDs in the crosswalk, preserve event provenance, and avoid counting the same event twice. |
| Unknown or missing consent | Keep the profile eligible for data quality work, not for a production send. |
Run a pre-send reconciliation that compares counts by channel, subscription group, region, and suppression reason. Capture exceptions rather than silently coercing them to an opted-in state. Keep the source consent event and the target load record so a compliance reviewer can reconstruct the decision.
How do I export and rebuild Braze segments in Salesforce Marketing Cloud?
Export both the segment definition and representative membership, then recreate the logic in Salesforce Marketing Cloud and measure parity. Salesforce Marketing Cloud documentation lists Connect API operations to retrieve, create, modify, delete, and publish segments and to retrieve segment members; use those operations where they fit your target architecture.
Export what defines an audience
- Segment name, Braze ID or API identifier, tags, description, filter clauses, nesting, and refresh timing.
- Analytics-tracking status and the date it was enabled.
- A dated member sample or full member list, with the identifier used to select each member.
- Dependencies on custom attributes, custom events, purchases, subscription groups, and campaign history.
Braze states that segment analytics tracking does not backfill revenue and purchase data from before tracking was enabled. Therefore, a segment that appears to depend on historical revenue may not reproduce the same population simply by turning on tracking in the target.
Recreate and compare
- Create a target audience definition with the same business meaning, not merely the same label.
- Map each Braze field to a Salesforce data-extension field or event source, documenting type conversions and missing values.
- Publish the target segment only in a non-sending state.
- Compare total counts and a deterministic sample of members. Investigate every mismatch caused by identity, time zone, null handling, event retention, or filter semantics.
- Store the Braze definition beside the Salesforce definition and assign a version number to each change.
Label the outcome equivalent when the population and refresh behavior match, approximate when a documented semantic difference remains, or manual redesign when the original logic cannot be represented safely.
Can I move Braze campaigns and Canvases directly into Journey Builder?
No universal one-to-one importer is established. Treat every Braze campaign or Canvas as a design specification and rebuild it in Journey Builder, preserving the business intent while explicitly redesigning unsupported or ambiguous behavior.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
| Braze element | Salesforce Marketing Cloud design decision | Classification to record |
|---|---|---|
| Entry trigger or scheduled audience | Choose a data-extension entry source, event entry, or scheduled audience refresh; document timing and re-entry. | Equivalent, approximate, or manual redesign. |
| Wait and time window | Map the delay, time zone, business-hour rule, and eligibility expiry; test daylight-saving transitions where relevant. | Equivalent or approximate. |
| Branching and decision filters | Recreate each branch from the mapped profile and event fields; define null and late-arriving-event behavior. | Equivalent or manual redesign. |
| Message variants and personalization | Rebuild content blocks, localization, fallback values, links, and channel-specific rendering. | Equivalent or manual redesign. |
| Frequency caps and suppression | Implement target contact rules, exclusion audiences, subscription checks, and global policies together. | Approximate unless behavior is proven equivalent. |
| Control group | Recreate the holdout assignment and persist membership for reporting and re-entry decisions. | Equivalent or manual redesign. |
| Conversion event and attribution | Map the event, attribution window, deduplication rule, and reporting owner. | Approximate or manual redesign. |
Build an asset packet for each journey
For every source asset, attach the source IDs, screenshots or exported definitions, audience version, message versions, trigger and wait logic, suppression rules, conversion definition, test cases, and named approver. This packet becomes the review record when a target journey intentionally differs from Braze.
Test behavior, not just configuration
Use synthetic profiles representing each branch: eligible, suppressed, missing an attribute, receiving a late event, in a control group, and entering twice. Verify that the target journey makes the same decision at each step or that the approved redesign is documented. Render messages in every production channel and locale before the parallel run.
How do I move Braze events, attributes, purchases, and profile history?
Create an event dictionary before loading data. Braze’s API supports user attributes, custom events, and purchases, and Braze describes the API as useful both for importing historical data and for continuous updates that are not triggered in Braze.
| Dictionary field | What to define |
|---|---|
| Event name | Exact source name, case sensitivity, and target name if transformed. |
| User key | Source external ID, anonymous ID, target ContactKey, and crosswalk rule. |
| Timestamp | Original timestamp, time zone or UTC status, and late-arrival policy. |
| Properties | Names, types, allowed values, null behavior, and sensitive-data classification. |
| Source | Braze API, warehouse, Currents, data lake, or another approved producer. |
| Retention | Required lookback, archival location, and deletion or minimization rule. |
Load in dependency order
- Load the identity crosswalk and deduplication results.
- Load profile attributes and subscription or consent states.
- Load event and purchase history with source timestamps and run IDs.
- Load current deltas and configure the continuous update path.
- Run referential-integrity checks so every event points to a valid target identity or an explicitly quarantined record.
Preserve the original event payload when policy permits, but also store normalized fields that journeys can evaluate consistently. Keep a replayable rejected-record queue rather than dropping malformed events.
Recommended Free Tools
How do I recover history older than Braze’s 90-day export window?
Do not assume a complete historical timeline is available in a segment user export. Braze documents that custom_events, purchases, campaigns_received, and canvases_received in that export contain only the last 90 days.
Before decommissioning Braze, identify older records in warehouse exports, Currents, Snowflake sharing, existing data-lake records, or another approved system. Braze describes Currents as a granular stream, so verify the event types, start date, retention, schema, and delivery gaps for the stream you intend to use. Reconcile the recovered source against Braze counts by day and event type before loading it into Salesforce.
Document what cannot be reconstructed
For every missing period or field, record the date range, affected asset, reason, alternative source checked, and reporting impact. Keep historical campaign and Canvas definitions even when member-level receipt data is unavailable; the definition may still be required to explain a past decision or consent record.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Which migration approach should I choose?
A phased migration with a controlled parallel run is usually safer for a large or high-risk estate because it exposes identity, consent, and behavior differences before the final switch. A big-bang cutover can be appropriate only when the inventory is small, the target mappings are proven, and rollback can be executed quickly.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match| Approach | Extraction completeness | Historical retention | Behavior and audience risk | Rollback readiness | Operational effort |
|---|---|---|---|---|---|
| Big bang | One coordinated export and load | Depends on completing all recovery work first | High if mappings are untested | Requires a tested full reversal | Shorter calendar window, intense preparation |
| Phased by brand, region, or journey family | Each wave has a bounded scope | Can prioritize high-value history first | Lower blast radius; cross-wave identity must be controlled | Rollback one wave while others continue | More coordination and temporary dual operations |
| Parallel run before cutover | Supports repeated deltas and reconciliation | Best opportunity to expose missing history | Direct comparison of sends, events, and conversions | Keep Braze active until exit criteria pass | Highest temporary operating cost |
Choose using extraction completeness, historical retention, identity and consent fidelity, audience parity, campaign behavior parity, event latency, API rate and throughput constraints, observability and replay, rollback readiness, operational ownership, and total implementation effort. Record the decision and the thresholds that would force a pause.
How do I validate the Salesforce build before cutover?
Validation must compare source and target outcomes, not just whether records loaded. Build a signed test pack for each wave and retain the input, output, discrepancy, owner, and disposition.
- Counts: compare exported objects, profiles, events, purchases, audience totals, and rejected rows.
- Membership: compare deterministic member samples and investigate every mismatch category.
- Event totals: compare totals by day, event name, source, and key property.
- Identity: check duplicate rates, anonymous-to-known links, orphan events, and crosswalk collisions.
- Consent: compare opt-in, opt-out, subscription-group, suppression, and regional states before enabling a send.
- Rendering: test personalization, fallback values, links, localization, and channel-specific output.
- Timing: test waits, time zones, entry windows, re-entry, late events, and frequency controls.
- Unsubscribes: submit test opt-outs and confirm that future eligibility is blocked in every relevant journey.
- Conversions: verify event receipt, attribution windows, control-group treatment, and deduplication.
- Operations: inspect API errors, import failures, queue backlogs, monitoring alerts, and replay procedures.
Set measurable exit criteria
Define acceptable variance separately for records, audience membership, event totals, consent states, rendering defects, and delivery errors. A wave is not ready because an administrator approves the journey; it is ready when the evidence meets the pre-agreed thresholds and unresolved differences have an owner and a documented business decision.
How do I run the parallel period and cut over safely?
Run a controlled parallel period in which Salesforce journeys are exercised against production-like data while Braze remains the sending authority. If both systems send to the same person, use explicit holdouts or non-delivery test paths; never allow accidental duplicate production messages.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Freeze design: stop untracked changes to Braze campaigns, segments, templates, consent rules, and event schemas. Log any emergency change in both systems.
- Export the final delta: capture profiles, consent changes, events, purchases, campaign changes, and segment changes since the last successful run.
- Reconcile: compare final source and target counts, audience samples, event totals, and suppression states. Resolve or formally accept discrepancies.
- Activate in waves: enable Salesforce journeys by agreed business or regional group, with monitoring on every wave.
- Watch production signals: delivery, bounces, unsubscribes, event latency, conversion attribution, import errors, and support or compliance incidents.
- Declare completion: only after each wave meets its exit criteria and the owner signs the evidence pack.
- Retain and decommission deliberately: preserve immutable exports, mapping tables, test results, consent evidence, and rollback instructions before disabling Braze access or data flows.
Define rollback before activation
A rollback plan should name the person who can pause Salesforce journeys, the last trusted Braze configuration, the delta needed to restore it, and the data that must not be resent. Set explicit rollback triggers such as unacceptable consent discrepancies, duplicate sends, material audience drift, sustained event loss, or a conversion-tracking failure. Keep rollback instructions executable by an on-call operator, not only by the migration author.
What evidence should remain after Braze is retired?
Retain an immutable package containing every export file and checksum, request and response metadata, crosswalk tables, source and target definitions, consent and suppression reconciliation, event dictionary, transformation code or configuration, discrepancy decisions, rendering tests, parallel-run results, cutover timestamps, and rollback instructions. Restrict access according to the data’s sensitivity and retention policy.
Keep enough lineage to answer four questions later: which Braze asset produced a contact, which source event or attribute qualified that contact, which Salesforce journey replaced the behavior, and which consent state permitted or blocked the message. Archive inactive definitions and historical reports even when they are not recreated as active journeys.
What are the most common migration failures?
- Using only dashboard CSVs: large exports hit Braze’s base 500,000-row CSV limit. Use APIs or connected cloud delivery and reconcile pagination.
- Assuming segment exports contain all history: selected activity fields are limited to 90 days. Recover older records before shutdown.
- Matching people by email alone: shared, changed, or mistyped addresses create merges and orphan events. Use an approved identity hierarchy and review queue.
- Copying names instead of logic: a segment or journey with the same label can still have different null, time-zone, re-entry, or suppression semantics.
- Ignoring consent until launch: loading an opt-in without its source, timestamp, channel, or region makes the record difficult to defend and unsafe to activate.
- Rebuilding content without conversion rules: messages may render correctly while attribution, control groups, or deduplication silently change.
- Overwriting exports: without run IDs and immutable files, you cannot explain which source state produced a target record or replay a failed load.
- Cutting over without deltas: changes made after the initial export disappear. Freeze changes and run a final delta reconciliation.
What is the practical migration sequence?
Use this order when turning the plan into a delivery schedule:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Approve scope, owners, data classifications, retention rules, and rollback authority.
- Inventory every Braze asset and classify it as active, paused, test, one-time, or archive.
- Define the authoritative identity key, consent precedence, and crosswalk schema.
- Run sample exports, validate schemas, configure durable storage, and capture export metadata.
- Execute full and delta exports for definitions, profiles, segments, events, purchases, sessions, and KPIs.
- Recover pre-90-day history from approved sources and reconcile daily totals.
- Normalize data and load identity, consent, profile, event, and purchase layers.
- Rebuild audiences, then campaigns and Canvases, labeling each mapping’s fidelity.
- Test synthetic profiles, rendering, waits, branches, suppression, unsubscribes, and conversions.
- Run the parallel period, enforce no-duplicate-send controls, and measure exit criteria.
- Freeze Braze, export the final delta, activate Salesforce journeys in waves, and monitor.
- Archive evidence and keep the rollback path until the agreed stabilization period ends.
Frequently Asked Questions
Should inactive Braze campaigns be rebuilt in Salesforce Marketing Cloud?
Usually not as active journeys. Preserve their definitions and identifiers for audit and historical interpretation, and rebuild them only when a named owner confirms a continuing business or compliance need.
How can I prevent duplicate events during a replay?
Give each load an immutable run ID and use a deterministic event key made from the source user identifier, event name, original timestamp, and an approved uniqueness field. Reject or quarantine a key already marked as processed instead of inserting it again.
What should I do when a Braze segment has no exact Salesforce equivalent?
Keep the original filter beside the target definition, document the semantic difference, and label the result approximate or manual redesign. Obtain business approval before using that audience for a production send.
When is it safe to delete the Braze export files?
Do not delete them at cutover. Keep immutable exports, checksums, mapping evidence, consent reconciliation, and rollback instructions for the retention period required by your compliance and operational policies.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
