# Should I migrate from Zoomin

Zoomin is unstructured knowledge. It is not a golden record. Do not migrate documents into an identity.

**Published:** 2026-06-17
**Canonical:** https://synconai.com/should-i-migrate-from-zoomin
**Author:** SynconAI Architecture Team

## In short

Salesforce completed the Zoomin acquisition on 1 November 2024. Zoomin is unstructured knowledge, not a golden record. A Knowledge article already holds a published answer. Identity resolution builds a profile key, and it does not absorb a document. Data Cloud was renamed Data 360 on 14 October 2025. Do not migrate documents into an identity. This page states no price and no end date.

## Sources

- **Salesforce Signs Definitive Agreement to Acquire Zoomin** (retrieved 2024-11-01)
  https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-zoomin/
  > Salesforce completed its acquisition of Zoomin on November 1, 2024.

## What to take away

- Zoomin is unstructured knowledge. The close was 1 November 2024. A document is not a golden record.
- Data Cloud was renamed Data 360 on 14 October 2025. Say the rename on its own date.
- A Knowledge article already holds a published answer. Do not migrate documents into an identity.
- Alternatives sit unranked. This page invents no AppExchange listing, price, screen, or shutdown date.

## The guide

A team drops a folder of PDFs into a brief and asks for the customer golden record. The folder holds manuals, policy notes, and a few files nobody can date. The request treats that pile as a person. It is not a person. Zoomin is unstructured knowledge. Migrating it means deciding which documents may be cited, by whom, and what happens when a document and a record disagree. It does not mean pouring the folder into an identity.

Salesforce completed the acquisition. The announcement tied that work to knowledge and to grounding, and it used the name Data Cloud. The rename came later, and this page will say it as its own sentence. Data Cloud was renamed Data 360 on 14 October 2025. Use Data Cloud when you quote what the acquisition announcement tied the work to. Use Data 360 when you mean the product name after that date. They are the same product across a rename. They are not a new promise that a document has become a profile. The only sentence this page quotes from the announcement is the completion line. "Salesforce completed its acquisition of Zoomin on November 1, 2024."

## Should you migrate

Migrate a source when it has an owner, a review date, and a rule for disagreement. A shipping policy, two pages, last reviewed by a person you can name, is a source. A drive called final is not. The agent, if you use one, may cite the policy. The order record still wins for the date the order system returned. The policy may explain the window. It may not overwrite the date.

Do not migrate because a folder exists. Volume is not a design. The cited page does not publish a shutdown date. You are not late. Leave the files where they are until each source you mean to cite has an owner. Stale is a status a person sets, or a review a person misses. Put the review on a calendar you already keep.

## A document is not an identity

The failure this page refuses is a migration that writes documents into a unified profile. A profile answers which source records refer to the same person. A document answers what a person is allowed to say about a policy or a product. Those questions use different objects. Mixing them is how a PDF starts writing fields on an account.

Do not migrate documents into an identity. Do not call the result a golden record. There is no golden record on this page. If profile unification is a project you already run, it keeps its own rules and its own owners. It does not gain a library because a knowledge folder was nearby.

## What the software is now

Salesforce owns Zoomin. The completion date is 1 November 2024. What the software is now is unstructured knowledge you might cite. It is not a master customer record. It is not a screen this page will draw. The cited page does not publish a price. Whether Data 360, or a grounding feature, is on your contract is a question for that contract. This page will not mark it as included because an announcement mentioned the old name.

If your org still has a document system under the old brand, that system is an operational fact for its owner. This page will not redraw it. If you only have a folder, the folder is the scope clue. It is not a profile.

## The three pages

This page answers whether you should migrate, what the software is now, how a document compares with native knowledge and with identity, and which alternatives sit unranked.

The implementation page is [Zoomin, knowledge, and grounding](/zoomin-agentforce-knowledge). Use it for sources, owners, and what an agent may cite. The what-happened page is [What happened to Zoomin](/what-happened-to-zoomin). Use it for ownership, the date, the blank price, and the absent end date. The integration page is [Integrating Zoomin with Salesforce](/integrating-zoomin-with-salesforce). Use it when a document must be connected without becoming a person. Read Data 360 material for the rename and the profile rules. Do not ask the knowledge pages to unify customers.

## Versus the article and the profile you already have

A Knowledge article already holds a published answer. It has a title, a publication status, an owner who can edit it, and channels where it may appear. Drafts stay unpublished. A person can point at the article and say whether it is current. That is structured knowledge. It already answers what the organisation is willing to say, in a form a colleague can maintain.

Identity resolution, where you run it in Data 360, already does a different job. It builds a unified profile from profile sources you chose to match, such as person records that share a rule you defined. The profile is a key across those sources. It is not a golden record. It does not pick a winning value and overwrite the rest. It does not read a policy PDF and decide the customer's phone number. That is the native identity behaviour. It already answers which records belong together. It does not answer what a manual says.

Only after those two descriptions does a comparison count. Zoomin is unstructured knowledge: documents, not profiles. A document can sit beside an answer as something an agent may cite, if the owner and the allow list say so. It does not become the article, and it does not become the profile. Migrating documents into an identity skips both native jobs and invents a third one this page will not sell.

When a document and a CRM field disagree, write the winner before you migrate. The order system wins for the order date. The article may explain the window. The profile is not a contestant. If the brief cannot say that, you are not ready. You are about to let a file edit a person.

## What you must not move

Do not migrate a whole drive. List sources as systems: a knowledge base you already publish, a file store security has accepted, a documentation set with a publisher. For each, name the owner and the refresh. A source with no owner will be cited after it is wrong.

Do not widen sharing so a demo can cite a restricted policy. The running user sees what that user can see. Fix the user or leave the document out. Do not treat "final" in a file name as clearance from counsel.

Languages are a scope choice. A policy in one language cited to a person in another is a confident error. If you operate in more than one language, say which sources exist in which language, and what happens when the match is missing. A transfer to a person is an acceptable answer. Invention is not. Put that choice on the paper path before you migrate a second language.

Grounding, if you use it, should show a passage a person can open. Connecting a source in Data 360 is a licence question. This page will not tell you the connection is included. Some features are add-ons. If you do not know, the cell stays blank. A migration that assumes the connection because the announcement mentioned Data Cloud has spent money you have not confirmed. Check the contract. Then cite the document, or do not.

A document and a profile can sit in the same programme only if the brief names two owners and two failures. The knowledge owner says when the file is stale. The identity owner says which person sources may match. The knowledge failure is a citation with no passage. The identity failure is a document written onto a person. If the brief has one owner for both, you have already mixed them. Split the brief before you migrate either. Data Cloud was renamed Data 360 on 14 October 2025, and the rename does not merge those jobs.

## Alternatives, without a rank

People search for alternatives after the acquisition, and for an alternative on AppExchange. This page has not been shown an AppExchange listing. It will not invent a listing, a rating, or a rank.

One way is to keep publishing Knowledge articles as you do now, and leave the acquired brand as history. Another way is to cite a named set of current documents, with owners, without writing them into profiles. Another way is to run identity resolution on profile sources you already trust, as its own project, with no PDFs in the match rule. Another way is to evaluate a different knowledge tool on your own criteria.

None of these is placed first. The gate is whether the thing you would move is a document with an owner or a person you hope the document will complete. If it is a person, you are in the wrong migration.

## A walkthrough you can finish on paper

Write one document title. Write the owner. Write the review date. Write who may cite it, and who must not. Write the field that wins when the document disagrees with a record. Write that the document will not be loaded as a profile. Write whether Data 360 is on your contract, or write that you do not know and the cell is blank. Stop on a blank line that is not the contract cell. The contract cell is allowed to be blank. The owner is not.

Take the source list to the implementation page. Leave price and shutdown on the what-happened page. Take the ban on documents-as-identity to the integration page. If a proposal says golden record, send it back.

## The first citations

If you do cite a pilot set, judge it by whether a person can open the source behind the answer. A fluent paragraph with no passage to check is the failure, even when the paragraph happens to be right. The next one will be wrong in the same voice. Pull that source back until the citation is real. Do not add the rest of the drive because the first file sounded plausible.

A pack goes wrong when the folder is labelled as the customer record, the rename is ignored, and a price is typed for "Data Cloud" without opening the contract. Data Cloud was renamed Data 360 on 14 October 2025. The acquisition closed earlier, on 1 November 2024. Keep the dates apart. Keep the document apart from the person.

::: warn
Do not migrate documents into an identity, and do not call the result a golden record. Zoomin is unstructured knowledge. Data Cloud was renamed Data 360 on 14 October 2025. The close was 1 November 2024. This page gives no price, no screen, and no end date.
:::

| Decision | You may proceed when | Stop when |
| --- | --- | --- |
| Migrate this source | Owner, review, and the disagreement rule are named | The brief is a folder |
| Identity | Profiles stay on profile sources | A document is loaded as a person |
| Native comparison | You have said what an article and a profile already do | The comparison promises a golden record |
| Rename | Data 360 is used for the name after 14 October 2025 | The old name and the new name are treated as two products |
| Alternative | The ways sit unranked | An AppExchange listing or a rank was invented |
| Price and end date | Both cells are blank | A figure or a quarter was typed to fill a template |

Bring the table to the meeting. If a document is in the identity row, take it out before anyone prices the work. The implementation page can price a source with an owner. It cannot price a golden record this page refused.

## Questions

### Should I migrate from Zoomin to Salesforce?

Migrate a document source only when it has an owner, a review, and a rule for when it disagrees with a record. Salesforce completed the acquisition on 1 November 2024. Zoomin is unstructured knowledge. Do not pour documents into an identity, and do not invent a shutdown date.

### What is Zoomin software now?

Zoomin manages unstructured knowledge. Salesforce owns it after 1 November 2024. It is not a golden record and not a current screen this page will describe. Data Cloud was renamed Data 360 on 14 October 2025. Use the new name for the product after that date. The cited page publishes no price and no end date.

### How does Zoomin compare with native Salesforce knowledge and identity?

A Knowledge article already holds a published answer with an owner and a status. Identity resolution builds a profile key from profile sources. That key is not a golden record, and it does not absorb a PDF. A Zoomin document may be cited. It is not either of those native objects.

### What are the alternatives after the Zoomin acquisition?

This page does not rank alternatives and has not been shown an AppExchange listing. Ways that sit side by side include staying with Knowledge articles, citing a named document set without touching profiles, running identity resolution on its own, or evaluating another knowledge tool yourself.

### Should documents be migrated into a unified profile?

No. Do not migrate documents into an identity. A profile matches person sources. A document is something you might cite. Mixing them lets a file write fields on an account. There is no golden record on this page.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Data 360 (https://synconai.com/salesforce-data-360-services.html).