ChatGPT
Claude
Google AI
Copilot
The cutover plan usually enters the weekend already agreed. Somebody says documents are now CRM records because the acquisition completed, and the Quip library and the Account load can share a Saturday, because the agreement feels settled: one date means one migration. At 9am the load created accounts. The documents stayed in Quip, which was the right place, and the project manager ticked both lines as one milestone. The agreement is the problem.
On Monday the argument was about a missing billing field. That field had never been a paragraph in a Quip document. The document owners spent the week exporting files into a rich-text area, and the accounts were still wrong. Two jobs had been scoped as one because a completion date was treated as a data model. A completion is a date. It is not a field list.
The distinction that matters is which thing is moving. Salesforce completed the Quip acquisition on 26 August 2016. Salesforce owns Quip. Quip is documents and spreadsheets. People write in it, comment in it, and share a link. That work can sit beside a CRM record. It is not the record. A document moving into Quip is not an Account migration. The amount, the close date, and the owner still live on the opportunity. The completion in 2016 did not move those fields into a paragraph.
What follows are the questions that split the weekend. A good answer names the library, the billing field, the completion date, or the contract. A general answer ticks a milestone that did not finish the account.
The questions, and what a bad answer signals
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| 1. What the completion actually did | The person who wrote the Saturday plan | A date is being treated as an Account data model |
| 2. Who owns the document, and who owns the billing field | The document admin and the account owner, by name | One migration is being staffed for two estates |
| 3. What date goes in the pack | Whoever is writing the timeline | The completion is being rewritten as a cutover |
| 4. Where the price is written | Procurement, from the contract | A completion sentence is being read as a figure |
| 5. Whether there is an end date | Whoever ordered the rich-text export | 26 August 2016 is being read as an expiry |
1. What did 26 August 2016 complete?
The question is not whether the acquisitions list is real. It is what that one sentence names, and which objects the Saturday plan has added on top of it.
Salesforce completed the Quip acquisition on 26 August 2016. The acquisitions page cited here states that completion in one sentence: "August 26, 2016: Salesforce completed its acquisition of Quip." Use the sentence as a date. It does not describe your folders, your account fields, or your Saturday load. It does not say a document became an Account. It does not say the product was shut down. It also does not say why Salesforce acquired Quip, or why Quip sold. Read it, write 26 August 2016 in the pack, and stop adding objects the sentence does not name.
Quip is documents and spreadsheets. A seller can keep a briefing document next to an opportunity. The amount, the close date, and the owner still live on the opportunity. Customers who already keep documents in Quip keep documents in Quip. The completion changed the owner of the product. On the facts used here, customers were not switched off Quip by the completion.
What happened, for a customer, is a completed acquisition and a product that is still documents and spreadsheets. What did not happen is a shutdown, a published price on the cited page, or a rule that a file migration and an Account migration are the same project. If a timeline shows Quip becoming the CRM on that August date, ask for the sentence. The sentence is a completion. It names Quip. It does not name Account.
A good answer sounds like the project manager reading the quoted sentence aloud and writing 26 August 2016, then splitting the library and the Account load into two lines before the weekend.
A bad answer sounds like "documents are CRM records now, tick both on Saturday." On Monday the billing field is still missing, and the export into rich text has started.
Keep one note in the programme folder. Owner: Salesforce. Completed: 26 August 2016. What it is: documents and spreadsheets. A new joiner can read the note before they add the document library to a data-load workbook.
2. Who owns the document, and who owns the billing field?
Salesforce owns Quip. You do not own the product because you have a Salesforce org. Your organisation owns the documents you wrote, the people who may edit them, and the CRM records those documents might mention. Those are different estates. A risk register that lists one owner and one migration for both will export the wrong thing on Saturday.
Is Quip owned by Salesforce? Yes. Did Salesforce buy Quip? Yes. Who owns Quip? Salesforce. Say the three answers the same way in the steering pack, the vendor form, and the support template. A form that still treats Quip as an unrelated company, and ignores the Salesforce relationship, is stale. A form that treats a Quip document as an Account record is also wrong. Ownership of the company is not the same fact as a shared data model.
The acquisition did not make the document the system of record for the customer. A contract, a meeting note, and a spreadsheet of draft numbers can live in Quip. The account you invoice from should have an owner and a field list you can name. Salesforce owning Quip does not choose that field list. If a supplier asks who owns the product, give them Salesforce and 26 August 2016.
A good answer sounds like a named document admin who can say which file is current, and a named account owner who can say who may edit the billing field, with those two names on different lines of the plan.
A bad answer sounds like one owner and one migration for the library and the accounts. The war room cannot say which system it is watching when Monday's argument starts.
The document job names the library, the editors, and what "current" means when two copies exist. The account job names the object, the external id, and who may edit the billing field. If a single weekend plan contains both and names neither, send it back. The completion date does not glue them together.
3. What date goes in the pack?
When did Salesforce acquire Quip? The completion was 26 August 2016. That is the date the cited page states, and it is the date to use. Do not shift it to a month because a slide has less room. Do not replace it with a year alone when the day is in the sentence. Write 26 August 2016, which is the same calendar day as the quoted American form, and label the source.
Put that date on the timeline as the completion. Do not add a second corporate date. Your own go-live for a document space, if you have one, is a different line, and it is yours. A search for a timeline that includes Quip should return the completion, the owner, and the statement that the product is documents and spreadsheets. It should not return an Account cutover.
The page cited here is the Salesforce acquisitions list entry for that day. It is not a price sheet and it is not a migration guide. State the completion. Send a reader who wants the legal instrument to the contract. A contract signature and a completion date can both be true. Write both, and label which document each one came from, so a later reader does not treat the acquisitions sentence as a licence.
A good answer sounds like 26 August 2016 written once, sourced to the acquisitions sentence, with the Saturday load dated separately and labelled as yours.
A bad answer sounds like "late 2016" on the board pack, or the completion date reused as the cutover, so an auditor cannot tell a close from a data load.
4. Where is the price written?
How much did Salesforce pay for Quip? The page this guide cites does not publish a purchase price or a licence fee. How much was Quip sold for? Same answer. A Salesforce Quip acquisition price does not appear on that page. The quoted sentence is a completion on a date. It is not a figure. A blank is more honest than a borrowed number beside a real date.
The deal price, even if another document later shows you one, is not your licence. A historical figure would not tell you what you pay to keep a document space this year. Your licence is the contract in your drawer. If the contract is silent, write that the price is not in the paper you are holding. Procurement can ask the account team for the commercial paper. That paper is the price that binds you.
What you pay a partner to move documents, and what you pay a partner to load accounts, are two statements of work if both exist. Neither figure is the 2016 purchase price. A quote that uses one number for both jobs has already mixed a file with a record.
A good answer sounds like procurement stating the document-space fee from the contract, or the silence, and a separate statement of work if an Account load exists at all.
A bad answer sounds like a single number, taken from a video or a forum, sitting beside 26 August 2016 and funding both the export and the account load.
5. Is there an end date, and which job is actually failing?
Was Quip shut down or given a sunset date? No end date is stated here. A completion is not a shutdown. A keyword that pairs the product with sunset is a question. The answer is that no end date is stated. 26 August 2016 is the day the acquisition completed. It is not an expiry. Customers still use Quip for documents and spreadsheets. The name on the cited page is still Quip. You can still ask for it by that name.
If a vendor tells you to export everything out of Quip because Salesforce bought it, ask for the retirement notice. A date in a search box is not a notice. A support template that has already called every Quip file an Account attachment will send the question to the wrong queue, and the billing field will still be missing.
Confirm your own contract term, your renewal, and the person who administers the document space. Those are your dates. They are not a product sunset. A forced export into rich text, because someone said the product was finished, loses comments, history, and the people who knew which file was current. Leave Quip in place until you have a written reason to move a specific library, tested, with an owner. That move is a document project. It is not an Account migration, and it is not a conclusion from 2016.
People search for a migration because the word acquisition sounds like a move. The move, if you need one, is a file from one document space to another, or a record from one org to another. They fail in different ways. A broken document link does not roll back an account load. A duplicate account does not restore a comment thread. Write the failure you are actually worried about, and staff that failure. If a briefing document should sit beside an opportunity, link it. Do not paste the opportunity into the document and call the document the book of record.
A good answer sounds like the document admin keeping the library in Quip, with the renewal read from the contract, and the account owner fixing the billing field on the account.
A bad answer sounds like "export everything, the product finished in 2016." Comments and history go with the export, and the missing field is still not a paragraph.
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
The document space and the account load live on the Quip page. Read it before you put both jobs on one weekend. The acquisition question ends when the pack can say the owner, the completion date, the missing price, and the missing end date.
