Enterprise DNA

Instead of Salesforce Data 360

Replace Data 360 reviews. Own your customer profiles.

We build your version around the sources and customer questions your business uses, bring across the agreed history and run it through Omni by Enterprise DNA.

Salesforce lists Data 360 Starter at US$60,000 a year. Other pricing models and limited free provisioning are available. Compare your own contract and required features.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Compare your subscription

Start with the work behind the customer profile

Data 360 covers a broad platform. Separate the customer-record review you need from the live connections and downstream work that your replacement must also support.

paid

The annual starting point

The published Data 360 Starter list price is US$60,000 a year. Your contract, entitlements and usage determine the actual bill.

database

Getting data in

Salesforce lists batch ingestion and zero-copy connections as free. The comparison should focus on what you use after the records arrive.

merge

Preparing and joining records

Preparation and unification are listed pricing activities. Your own review process keeps the source records and evidence behind each identity link.

groups

Building and using audiences

Segmentation and activation are part of the paid platform. We agree which destinations and approval steps your custom version must support.

search

Questions and sharing

Queries and sharing have their own usage treatment. Keep the answers you need and the rules that produced them under your control.

sync

Live processing

Streaming and real-time processing appear separately in the pricing model. We scope live connections against your actual operating requirements.

Your version

A customer profile with its evidence attached

Identity

Review a possible match before joining it

A household or business can share an email address. Keep the evidence that tells you whether two records describe the same person.

  • check Same-email candidates with different names flagged
  • check Source records preserved after a reviewed link
  • check Conflicting names and addresses visible together
  • check An operator and reason recorded for every link

Sources

Know where every answer came from

Keep customer history beside the owner and purpose of the source that supplied it.

  • check Source record references retained with the profile
  • check Stale imports and unlinked records counted
  • check Repeated imports skip identical records
  • check Changed identity details return the link to review

Responsibility

Keep review duties in the weekly work

Missing evidence becomes an assigned task. The data owner decides the action and records the result.

  • check Purpose and collection-notice gaps listed
  • check Retention review dates checked against today
  • check Preferences kept by channel and purpose
  • check Overdue actions closed only with evidence

Ownership

Keep the records and the decisions

Ask for the view your business needs and keep it with the database you own.

  • check A printable customer profile review record
  • check A source purpose and retention register
  • check A weekly view of freshness, conflicts and overdue work
  • check Your own fields and review rules added to your version

Make it yours

Design your own Salesforce Data 360 replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Data 360. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Data 360 replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Data 360 data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Customer Profiles for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Customer Profiles for Claude Code

Connected to your own database

Which records share an email, and which names need a closer look?

CRM:C001

Right record
STORE:S001
Left name
Mere Rangi
Right name
Mere Rangi
Shared email
mere@example.test
Review reason
same name and email; verify

CRM:C002

Right record
STORE:S002
Left name
Ben Cole
Right name
Jo Cole
Shared email
office@example.test
Review reason
shared email; names differ

Ask it anything

Ten questions your version answers

These examples run against the working database. Salesforce also offers analysis and identity tools; the difference here is owning and adapting your review workflow.

chat_bubble Which source has stopped arriving?
chat_bubble Which source has no accountable owner?
chat_bubble Which records share an email but have different names?
chat_bubble Which reviewed profile has conflicting email addresses?
chat_bubble Who linked this source record and on what evidence?
chat_bubble Which newsletter preference is the latest, including a withdrawal?
chat_bubble Which source records have reached our retention review date?
chat_bubble Which collection notices still need review?
chat_bubble Which review actions are overdue and who owns them?
chat_bubble Which identity changes broke a previous profile link?

Switching

How to switch from Salesforce Data 360

A move like this is mainly an authorised export, mapping your records and rules, and checking the imported data before you rely on it.

  1. 1

    Export the records you need

    Have your authorised Data 360 operator export the complete history you are authorised to bring, using Query API V2 responses with the documented projection. Get every batch and preserve its query IDs and completion flags. A mapped CSV with the same columns also works. Do not rely on the on-screen preview, because it is not a complete export.

  2. 2

    Test-load a sample

    Use the documented field mapping to prepare a sample, then run the import's test run before saving anything. The importer handles the saved export, not Salesforce authentication. Include only the records and history you have chosen to move. Saved matching rules, segments and preference history need separate mapping, so do not assume they come across automatically.

  3. 3

    Check the import results

    Review what the import reports about completion flags and record counts. Reconcile a sample and then the full export against the original query before relying on the new database. Review possible identity matches and changed identity details too. Same-email records are suggestions for review, not automatic links, and an identity change can remove an existing link for review.

  4. 4

    Run both systems side by side

    Keep your existing Data 360 process working while you test the replacement against the requirements you have agreed. Use this period to check that the imported records, reviewed identity links, source evidence and review work meet those requirements. The replacement is for customer-profile reviews from imported records, not live collection, streaming or activation.

  5. 5

    Switch off after testing

    Once the agreed requirements have been tested, confirm whether you still depend on Data 360 for live collection, downstream audiences, activation, streaming or other platform functions. This replacement does not cover those functions or the whole Data 360 platform. Switch off Data 360 only when you have confirmed those needs are handled elsewhere or are no longer required.

construction

Where the real effort goes

The main work is mapping your own fields and identity rules, then deciding how much customer history to bring. Matching rules, segments and preference history need separate mapping, and the export must be reconciled before you rely on it. If you have Enterprise DNA run the system for you, Enterprise DNA does this mapping and setup work with you.

Not ready for a call?

Get your Salesforce Data 360 switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Data 360, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want to run

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Import the documented Data 360 export projection and reconcile counts
  4. 4 Review identities, record evidence and adapt your rules
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your source mappings, fields and identity review rules
  • check Your agreed Salesforce Data 360 history brought across and checked
  • check A web front end or different stack when your team needs one
  • check Your connections, access requirements and review documents
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Agreed sources connected with authorised access
  • check Backups and data handling set for your business
  • check Your regular data review and follow-up kept working
Book a call with Sam

Questions

Instead of Salesforce Data 360, answered

Does the free version replace the whole Data 360 platform? expand_more

It runs customer-profile reviews from imported records. We scope live collection, downstream audiences, access controls and scale with you. Keep the existing process working until the replacement for your agreed requirements has been tested.

Can we bring our customer history across? expand_more

Yes, using a complete authorised export with the documented field mapping. The free importer checks supplied completion flags and record counts. Saved matching rules, segments and preference history need separate mapping. We reconcile a sample and the full export before relying on the new version.

Will it accidentally join two different people? expand_more

Matching email addresses create review candidates, not automatic links. A reviewer supplies identity evidence before joining records. The system retains conflicting values and the reason for each link. When an import changes identity details, the old link is removed for review.

Does it handle our privacy obligations? expand_more

It flags missing purpose and notice evidence, conflicting identity details and overdue retention reviews. These checks support the responsible owner rather than certify compliance. Recorded preferences do not authorise sending, and retention dates do not trigger automatic deletion. We agree the controls needed for your installation.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for agreed ongoing work. We first review your source history, identity rules, connections and operating needs. The free base has no licence charge. Hosting and the tools used to operate it have their own costs.

Bring the bill and one customer record you cannot trust

Spend 30 minutes with Sam. Show the sources, the duplicate that keeps returning and the work your team does to fix it. We map the history, rules and operating work your version needs.

Book 30 minutes with Sam Get the free version

Customer Profiles for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Data 360?

Get your version built