What happened to Own

The finance slide usually enters the room already agreed. Somebody puts approximately $1.9 billion into the licence model and names the CRM cutover "the Own migration", because the agreement feels settled: a company that was bought is now the place the data moves. People in the room still say OwnBackup. The plan is to restore Friday's backup into the new org on Saturday and call the data moved. The agreement is the problem. A close is a date and a deal figure. It is not a cutover method.

Nobody had listed which objects the job actually holds. Nobody had said what a restore does to records the new org has already changed. On Saturday the restore ran. Automation in the target sent mail. A field the new org does not have arrived blank. On Monday the two orgs disagreed, and the backup that was supposed to be the migration was the thing you needed in order to undo it.

The distinction that matters is what a backup is allowed to do. Salesforce completed the Own Company acquisition on 18 November 2024. People still search OwnBackup. Own Recover is now Salesforce Backup & Recover. The agreement was announced on 5 September 2024. The 5 September 2024 announcement said approximately $1.9 billion in cash, net of shares Salesforce already owned. That figure is the deal, not a licence. Backup copies what you configured it to copy. It does not invent the object model of the target, and it does not decide which of two versions of an account is the one the business meant.

What follows are the questions that stop a restore being booked as a cutover. A good answer names the objects, the org that receives them, the announcement figure with its qualifiers, or the contract. A general answer turns the undo copy into the migration.

#The questions, and what a bad answer signals

#1. What did the close complete?

The question is not whether the acquisition happened. It is whether anyone is treating the completion sentence as a method for Saturday.

Salesforce recorded the close in one sentence: "Salesforce completed its acquisition of Own Company on November 18, 2024." Read it as a date. Completion was 18 November 2024. The sentence does not describe your objects, your retention, or your Saturday plan. It does not say a restore is a cutover. It does not say the new org can be built by replaying a backup. If a proposal treats the date as a method, ask for the words. The words are a completion.

The product line has a name you should use as written. The product sentence is: "Own Recover, ranked the #1 Enterprise SaaS Backup by G2, is now Salesforce Backup & Recover." The sentence renames Own Recover to Salesforce Backup & Recover. It includes a G2 ranking inside the sentence. Quote it if you need the ranking. Do not extend it. Do not add a second award, a market share, or a claim that the ranking covers migration. The sentence says backup. Backup is the job. The G2 words stay inside that sentence. They are not a service level you can paste into a contract on your own authority, and they are not a promise about migration.

The sentences quoted here do not say why Salesforce acquired Own, or why the company sold. A motive added from a talk is not a source. The useful question is what you can restore, and which org receives it.

A good answer sounds like the person who booked Saturday reading the completion sentence as 18 November 2024, and the product sentence as a rename to Salesforce Backup & Recover, then taking "migration" off the slide.

A bad answer sounds like "the Own migration" as the name of a CRM cutover, with Friday's backup as the load. Automation sends mail, a field arrives blank, and Monday needs the backup to undo the backup.

What happened, for a customer, is a completed acquisition, a deal figure that is not your fee, and a product name that is now Salesforce Backup & Recover. What did not happen is a shutdown, or a new CRM called Own. If a slide says OwnBackup migration, correct the noun before you correct the date. The noun is backup. The completion is 18 November 2024. Neither is a data conversion.

#2. Who owns the policy, and which name do you type?

Salesforce owns Own Company. People still search OwnBackup, and the answer to who owns that search is the same. Salesforce. You do not own the product because you have an org to protect. Your organisation owns the backup policy, the person who may approve a deletion, and the org that receives a restore. Those are different from the vendor's ownership of the product.

Is Own owned by Salesforce? Yes. Did Salesforce buy Own? Yes. The completion was 18 November 2024. Who owns it? Salesforce. Say that in the steering pack, the vendor form, and the support template, and add the search name so a form that still says OwnBackup can be matched to Salesforce Backup & Recover. A form that treats Own as the new CRM is wrong. Ownership of the company is not a data model.

The acquisition did not make the backup the system of record. The org is the record. The backup is a copy from a time you choose. Salesforce owning the product does not decide which objects are in the job, or which org a restore may touch. If a supplier asks who owns it, give them Salesforce, the completion date, and both names.

A good answer sounds like a named person who may approve a deletion, saying Salesforce Backup & Recover in the new runbook, and OwnBackup only when they are helping someone search.

A bad answer sounds like "OwnBackup is the new CRM, and the search name is a second product we can migrate into." The habit outlasts the rename. The scope should not drift to follow the habit.

Keep OwnBackup in your notes so a search and a contract can find each other. Say Salesforce Backup & Recover in new documents. When a colleague searches OwnBackup, answer with the current name and the same scope.

#3. Which date is the announcement, and which is the close?

When did Salesforce acquire Own? The agreement was announced on 5 September 2024. Completion was 18 November 2024. Keep both dates, and label them. The announcement date is when the deal figure was stated. The completion date is when the cited close sentence says the acquisition finished. Do not collapse them into "autumn 2024" if a board pack needs to be checked later. Do not swap them. A price without a completion, or a completion described as the day the price was your fee, will be misread.

Put 5 September 2024 on the timeline as the announcement. Put 18 November 2024 on the timeline as the completion. Do not add a shutdown date. Your own first restore drill, if you run one, is a third date, and it is yours. A search for a timeline that includes Own, or OwnBackup, should return those two corporate dates, the current product name, and the statement that backup is not a migration.

The pages cited here state the completion and the product rename. State both. Send a reader who wants the legal instrument to the contract. The contract is where your term lives. The announcement figure is not that term.

A good answer sounds like two labelled dates: announced 5 September 2024, completed 18 November 2024, with the drill date, if you have one, on its own line.

A bad answer sounds like "autumn 2024" doing both jobs, or the September figure described as the day your fee started. A later check cannot tell an announcement from a close.

#4. What is the $1.9 billion figure?

How much did Salesforce pay? The 5 September 2024 announcement said approximately $1.9 billion in cash, net of shares Salesforce already owned. That is the deal, not a licence. How much was it sold for? That same announcement figure is the deal figure to repeat, and it is still not your fee. Do not add a second number. Do not drop the words "approximately" or "net of shares Salesforce already owned". Those words are part of the figure. A round billion, or a gross number invented beside it, is a different claim.

Your licence is the contract in your drawer. The deal figure does not tell you what you pay next year, what storage costs, or what a restore drill costs in your administrators' time. If the contract is silent, write that your fee is not the announcement. Procurement can ask the account team for the commercial paper. That paper is the price that binds you. A business case that pastes $1.9 billion into a cost per user has used a corporate close as a rate card.

Keep the history number in the history note. Keep the operating cost in the statement of work. The objects, the retention, and a drill are still not the deal figure.

A good answer sounds like finance saying the announcement figure in full, approximately $1.9 billion in cash, net of shares Salesforce already owned, and then reading this year's fee from the contract.

A bad answer sounds like "$1.9 billion" with the qualifiers dropped, pasted into a cost per user, as if the September announcement were a rate card for the Saturday restore.

#5. Is there an end date, and what does a restore actually do?

Was Own shut down or given a sunset date? No end date is stated here for Backup & Recover. A completion is not a shutdown. A rename from Own Recover to Salesforce Backup & Recover is not a retirement. People still search OwnBackup because the habit remains. The habit is not a second product you can switch off, and it is not proof the product ended. A keyword that pairs the name with sunset is a question. The answer is that no end date is stated.

If a vendor tells you to stop backing up because the company was bought, ask for the retirement notice. 18 November 2024 is the completion. It is not an expiry. Customers still need a copy they can restore. Say Salesforce Backup & Recover in new documents so the ticket reaches the right queue. Mention OwnBackup when you are helping someone search. Do not mention it as a product you move the CRM into.

Confirm your own contract term, your retention, and the person who can approve a deletion of copies. Those are your dates. They are not a product sunset. A plan that drops backups because the logo changed will discover the gap during the incident. Leave the job in place until you have a written list of what it holds, tested with one restore that does not pretend to be a cutover.

Restore writes that copy to an org you name, under rules you tested. It does not invent the object model of the target. A migration is a map. A backup does not contain that map unless you wrote it somewhere else. Decide what must be recoverable, and test a restore. The incident you are buying protection against is a bad import, a mistaken delete, or a week of edits you need to undo. Write the drill: who declares it, which objects come back, which org receives them, and how you stop automation first. A drill that has never been run is a setting, not a capability. A quote that includes only a licence name has not bought the drill.

A good answer sounds like the deletion approver naming the objects, the target org, and the step that stops automation before any restore, with the renewal read from the contract.

A bad answer sounds like "drop the backups, the logo changed," or a Saturday restore into a live org with automation on, called a migration. Monday is then an undo.

A DVD, a Reddit thread, a YouTube clip, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.

#Where the decision goes next

Objects, retention, and a restore that is not a cutover live on the Own backup page. Read it before anyone names a Saturday restore as the migration. The acquisition question ends when the pack can say the owner, both dates, the deal figure, and the missing end date.