ChatGPT
Claude
Google AI
Copilot
The migration file has one column: account name. The person who still does the industry work can name the step they completed this morning, and where they completed it. Around the table everyone already agrees the load is a Vlocity migration, because the names arrived. The file cannot name the step. The agreement is the problem. It is easy to reach, and it fits a column of parties, which is not the work.
A dropped step is compatible with an industry cloud you already run, an account that holds the organisation or the person you do business with and nothing further, a screen nobody has opened, and a date that says the vertical product must be emptied into accounts. Only a named step, with a place a person can still complete it, is a move. An account row will not name the step for you.
What follows are the questions that separate those explanations. Each has a good answer and a bad answer, and the difference is whether the answer names something specific: a step, a place, a person who did the work, a product. A general answer at this stage is what turns into a file of names.
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| 1. Which step was completed | The person who did the industry work this morning | The file is being treated as the process |
| 2. Does that step stay in the industry cloud | The team that will still complete it there | An account export is being treated as a more advanced version of the step |
| 3. Does the destination still contain the work | Whoever drew a screen to catch the drop | A sketch nobody can open is standing in for a place |
| 4. What does an account already hold | The administrator who can open the account | Contacts and opportunities are being asked to be the industry process |
| 5. What must the plan refuse | Whoever merged this with a CPQ cutover, a date, or a listing | Two products are being emptied because they appeared in the same search |
1. Which step is actually in the room?
The question is not whether Vlocity should be migrated. It is which step a person completed in the last week, in one sentence that is not the word account, and where they completed it.
A good answer sounds like the step in the words of the person who did it this morning, with the place they completed it, written down before any file is discussed.
A bad answer sounds like the account name is the step. If you cannot write the step without using the word account as the whole description, you are earlier than a migration. Stop. Ask the person who did the work. A programme that only has a column of names cannot be judged to have moved the work, because the work was never in the column.
People still say Vlocity because the word is on old designs and old contracts. The software is the industry clouds. The rebrand record says what the product became, and the sentence is quoted once: "Vlocity, acquired in 2020, became Salesforce Industries (or Industries Cloud) providing deep, industry-specific solutions."
The sentence says Salesforce Industries, or Industries Cloud, providing industry-specific solutions. Those are the industry clouds. The solutions are specific to an industry. They are not a thinner copy of a core account. If your organisation runs one of them, the steps in that industry are the software. The account beside them is not the whole of it.
2. Does the step still belong where it was completed?
If the team will still complete the step in the industry cloud, on purpose, the decision is to leave it. Leaving it is a finished answer. Copying account names into a core file is not a substitute for the step. A stay is allowed to be the majority of the list.
A good answer sounds like a named person who will keep completing that step in the industry cloud for another year, and who can show where they did it this morning.
A bad answer sounds like the vertical product should be emptied into accounts because the name changed. Count the steps you would keep in the industry cloud. Those steps are not a migration. The step someone completed this morning is evidence the industry work is live. Use the evidence.
There is no end date for the industry clouds in the material this decision is allowed to use. A date that says the vertical product must be emptied into accounts has invented a notice. Take the date off. Decide step by step. If no step moves, say so. An empty move list is a decision to keep the industry work where it runs.
3. What would a real place for the step be?
A destination is a place you can open, where the same step can still be completed, described in the words the person who does the work would use. A screen you have not opened is not a fact. If a real screen exists in your org, name it from the org. It is not named from this decision. An invented screen is not a destination.
A good answer sounds like a place the person who did the work can open, with the step still completable there, and with the account file set aside until that place exists.
A bad answer sounds like we will sketch an OmniStudio screen to catch the steps. Do not invent an OmniStudio screen. A sketch is not a destination. If the migration file contains only the account, the step has been dropped. Stop the file. Add the step as its own row, with a place, or admit you are not migrating that work. An account name cannot grow a step by being imported twice.
Do not bring the SteelBrick decision onto this one. A CPQ org whose metadata uses SBQQ is a different product, with its own cutover rule. No screen is invented here that pretends the two histories are one migration. If someone merges them because both words appeared in a search, split the meeting.
4. What does an account already hold?
On the core platform, an account is the organisation or the person you do business with. Contacts related to that account sit beside it. Opportunities related to that account sit beside it. The account already does that work. It holds the party and the relationships a core org is built to hold. It does that with no dependence on the Vlocity name.
It does not hold the industry steps. A step is the work a person still completes because the business is in that industry: an order of operations, a check, a status that means something in that trade. If the step is not a field you can point at on the account, copying the account does not copy the step. If the comparison starts from the account, write that limit before anyone compares anything.
A good answer sounds like an administrator who has opened the account, named the related contacts and opportunities, and said plainly that this morning's step is not a field on that record.
A bad answer sounds like loading names into the core org is the migration. The account can still be the party you do business with. It is not the step someone completed this morning. Ask which step, after the copy, a person can still complete. If the answer is silence, the copy dropped the work.
Native, for the core record, is the account as just described. Native, for the industry work, is the industry cloud the quoted sentence names. Those are different. The comparison starts only after both descriptions are in the room. If a box is a screen nobody can open, the box leaves.
Keep three lines apart. Account: the party. Industry step: the work. Industry cloud: the product the record names, with no end date in this record. A plan that cannot keep the three lines apart is not ready. There is no score.
5. What is the plan using instead of the step?
The substitutes are an invented screen, a date, a listing, and a merged CPQ story.
A good answer sounds like a refusal, written by the person who did the work, of four things: an OmniStudio screen nobody has opened, an end date for the industry clouds, an AppExchange listing as the step, and a SteelBrick cutover folded into the same file.
A bad answer sounds like the listing will restore the step the file dropped. No listing is invented here. An app, a publisher, a review count, and a price are not in the record being cited. A listing found independently is still not the decision. The decision remains the step. An app does not know which industry step was completed this morning. A listing is also not a licence to invent an OmniStudio screen. The industry clouds were not given an end date. Do not treat them as a retired product that a listing must replace. An AppExchange search will not restore a step the file dropped.
Other vertical tools exist. They are not ranked here, and they are not named in an order. Choose a tool only when the step is named and the place is real. If a slide arrives with ranks, replace the ranks with the step and the mark. A destination that is only a score, or only an account column, is not a destination.
What staying actually looks like
All five answers are measured against an alternative, and the alternative is usually left unstated, which flatters the account file.
State it. Staying means the person who did the work this morning keeps completing that step in the industry cloud, and the account continues to hold the party it already held. The word Vlocity remains on an old design. That is a label. The step is not. The cost of a false move is a file of names and a morning's work that nobody can finish, plus a screen that exists only on a slide.
There is a version of staying that is simply the correct decision. If the step still belongs in the industry cloud, the account export is not a more advanced version of the same step. An organisation that writes the steps first reaches any later place with a shorter list and no invented screen to maintain.
A good answer sounds like a list of steps marked stay, in the words of the people who complete them, and a separate list of real places that may be empty, produced by those people rather than by the owner of the account column.
A bad answer sounds like we cannot keep an industry product beside the account. The account was never the whole of the work. The step does not move because a column was easier to load.
Where the neighbouring questions live
What it costs to change a step you have actually named sits on the Vlocity implementation page. The purchase and the rename as history sit on what happened to Vlocity. The objects, and what you do when an industry step does not land, sit on integrating Vlocity with Salesforce.
