ChatGPT
Claude
Google AI
Copilot
A finance lead hears that Salesforce bought a company that turns sentences into SQL, and asks for a migration that lets every seller ask anything about the warehouse. The request sounds like access becoming simpler. It is a proposal to drop the grants. The close does not say that. A question is not permission to read every table.
This page answers whether you should migrate, what the software is now, how that compares with native Salesforce features, and what the alternatives are. The alternatives are not ranked. There is no price, no AppExchange listing, and no shutdown date on this page.
Should you migrate
Migrate, in the search, usually means "move Waii data into Salesforce" or "open the warehouse to anyone who can type". Neither reading is supported by the record this page cites. Do not migrate access by letting every asker see every row. If that is the plan, the answer is no.
A smaller decision can still be yes. You can allow a named role to ask, in ordinary language, about a named list of tables, and you can keep the generated SQL beside the answer so a person who can read SQL can check it. That is an access design. It moves no rows into a new home. It does not treat the sentence as a grant.
Write the decision against a table, not against the product name. "The billing mart may be asked about by the finance analysts who already have that role. The staging schema may not." Each sentence has an object and an audience. "Migrate Waii" has neither. Send it back until it does.
People want a walkthrough because a walkthrough feels like a sequence they can hand to a project manager. A click-path assumes a screen the close notice does not draw. The walkthrough you can defend is a list of tables, a role, five questions that must return no rows, and a rule that an unlisted table stays unlisted even when the question is clear. Clarity is not authorisation.
What Waii is now
The sentence this page quotes from the close notice is: "Salesforce completed its acquisition of Waii on August 15, 2025." The date in Australian order is 15 August 2025. Same day. Waii turns plain language into SQL. Salesforce planned to integrate that work into Data Cloud. Planned is a direction. It is not a switch this source says is already on in your org.
The rename has its own sentence, and this page quotes it unchanged: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." Put Data 360 on the diagram, in the statement of work, and in the briefing you give a new analyst. Old labels may linger in an application during a transition. The new name does not add a table, remove a grant, or decide that a question is allowed.
Keep the two dates apart. Waii closed on 15 August 2025, while the product was still being described as Data Cloud. The rename landed on 14 October 2025. A design written between those dates can be right about the intent and wrong about the label. Update the label. Re-read the grants. They do not update themselves because a product changed its name.
What the software is now, on these sources, stops at that capability and that name. The notices do not describe a Waii database of business records you extract. They do not say every Data 360 tenant gained a natural-language box on the morning of the close. Confirm what the contract includes. Do not treat a completion sentence as an entitlement.
A sentence is not a grant
Plain language is a way to ask. SQL is a way to read. The right to read sits on the identity that runs the SQL. If that identity can select from a table, a well formed question can return those rows. If you wanted the table closed, the question is not the control that closes it. The grant is.
This is the line teams skip because the interface is polite. An analyst asks a reasonable business question. The tool turns it into SQL and runs it with the rights it has. The failure was upstream. Someone gave the path a broad role so a demonstration would return rows. The demonstration then became the way the company reads the warehouse. Do not migrate access by copying that role forward and calling the copy a migration.
Natural language also hides which tables were used. A SQL statement can be reviewed. A sentence cannot, unless you keep the statement beside the answer. Require that. If the path returns a number and withholds the statement, you cannot tell whether it read a closed table, an approved mart, or both. Store the statement with the question, under the same retention rule as the result.
Write the audience down. A pilot of five analysts is a different risk from a channel of two hundred. Growing the audience is a new decision, because the same SQL in a larger room is a publication. "Every asker" is not an audience. It is the failure mode with a friendly name.
Versus native features
Salesforce already lets a person open a report, a list view, or a record they have access to. Those paths run as that person. They return rows the person's own rights allow. Data 360, under its current name, is where streaming and batch data can be brought together for the jobs your contract includes. None of that is a sentence that silently picks a wider role.
Waii, on this record, is a way to turn language into SQL, aimed at the data platform that is now called Data 360. A report a person built is a saved question with a known object. A sentence is a new question every time, and the SQL is the only way to see what it touched. Native reporting does not become wrong because a language tool exists. The language tool does not become a grant because the reporting already works.
This page does not rank them. A team whose questions are already answered by a report they trust does not need a new path that can see more tables. A team that wants ordinary language over a named mart still has to write the mart, the role, and the refusals. The comparison tells you which job you have. It does not crown a feature.
| Job | What this record says about Waii | What native features already do | What you still write |
|---|---|---|---|
| Answer from a report the person can run | Not described as a replacement for reports | The report runs as that user | Nothing, until the question is outside the report |
| Ask in a sentence about a warehouse table | Plain language becomes SQL | A list view does not open an unlisted schema | The table, the role, and the stored statement |
| Let every colleague see every row | Not in the close notice | Permissions still apply to the user | A refusal. Do not migrate access that way |
If a column is blank, leave it blank. A slide that says Data 360 and then shows every schema has used the new name to hide an old mistake. Fix the name. Then fix the list.
Alternatives, with no order
A search for a Waii alternative on AppExchange expects a package, a publisher, and a rank. This page has none of those. Naming one would invent a listing. The options below are ways to do the job. They are not in order, and none of them is the winner.
Keep the reports and list views people already run, under their own login. That option fits when the question has a stable shape and the object is already in Salesforce. You do not need a sentence layer to restate a report.
Ask through a named role against a named list of tables, and keep the SQL. That option fits when ordinary language would help, and you can point at the mart. It is an access project. It is not a data load, and it is not a gift of every row to every asker.
Give the analyst their existing warehouse role, so they see what they already see in the tool they use today. That option fits a small pilot. It does not fit a public channel. The audience is the risk, not the spelling of the question.
Do nothing new until the catalogue of tables exists. Waiting is a decision. The week after a close is a poor week to widen a role so a demo returns rows.
A partner who opens with a ranked shortlist, and a blank catalogue, has brought a directory you did not ask for. Put the rank away. Walk the tables. This page will not sort the options for you, and it will not invent a package to satisfy the AppExchange search.
What the walkthrough contains
A walkthrough that does not invent a screen has these lines.
The catalogue. Tables, views, or marts the path may use. Each line has an owner. Tables that are absent are out of scope, even if a question would be easier with them. Adding a table is a change, with the owner's yes.
The role. What it may read, and which columns stay closed. Pay, health, account numbers, and free-text notes are the usual columns to name. A table can be in the catalogue and still have columns closed.
The audience. Who may ask, and in which room the answer may appear. Write it down before the first question is tried in a shared channel.
The refusals. Five questions that must not return rows. A closed schema. Another region's payroll. A raw staging table. A table you have not listed. A request to show everything on a customer when the catalogue only holds a mart. Test them with the role you will keep.
The review. A person who can read SQL looks at a sample of statements during the pilot. They are checking for tables outside the catalogue. If they cannot keep up, the audience is too wide or the log is too thin.
The stop. When the path cannot answer from the catalogue, it says so. It does not reach for an unlisted table because the question was clear.
There is no figure on this page for the work, and there should not be. The announcement has no price. Your warehouse is not the announcement's warehouse. Price the list with your own scoping, or do not price it yet. Do not price a promise that any colleague may ask anything.
Where the other pages fit
The implementation page works the catalogue, the grants, and the refusals in full: Waii, plain-language SQL, and the Data 360 rename. Go there when you are naming tables. Do not go there for a dollar figure or a rank.
What happened, who owns Waii, the two dates, the missing price, and the missing end date are on what happened to Waii. Stay there when the question is the acquisition and the rename. Leave it when the question is which rows an asker may see.
The integration page is the boundary between a sentence and a table: integrating Waii with Salesforce. Read it when someone wants a connector. The connector still runs as an identity. It does not outrank the grant.
| Question | Where it belongs |
|---|---|
| Should we migrate? | This page. Not by letting every asker see every row. |
| What is the software now? | Plain language into SQL. Data Cloud is now Data 360. |
| Versus native? | Reports and list views run as the user. No winner is declared. |
| Alternatives? | Ways to ask, or to wait, with no order and no AppExchange listing. |
If the only artefact in the room is a screenshot of a result, you still do not know which tables were read. Ask for the SQL. If nobody can produce it, you are not ready to widen the audience. Update the diagram to say Data 360, and then read the grants again. The rename will not do that reading for you.
