Replacing shared links before they break

Every conversation link you shared with someone points at the account you are closing. When the account goes, so do the links — not with a redirect, not with an explanation, just a page that no longer resolves.

This is the only item in a switch with somebody else’s deadline attached, and it is discovered by them, later, when they click.

Why this one gets missed

A shared link does not feel like your data, so it never makes the inventory. You created it to send someone an explanation, it did its job, and the copy in their document became a permanent reference you have not thought about since.

The other reason is that there is no list. Some products show you what you have shared and some do not, and even where a list exists it does not tell you where the links ended up. The links live in other people’s documents, which is exactly where you cannot search.

Find them from both ends

Start with whatever the account offers. If there is a shared-links or published-content area of the settings, that is the authoritative list of what exists, and it is the fastest way to know the scale of the problem.

Then search where you sent them. Your own sent mail, your team chat history, and the ticketing or documentation systems you use — searching for the service’s domain in any of those surfaces the links you pasted. This is the half that finds where they actually are.

If your export is flattened and searchable, it may indicate which conversations were shared, which narrows the list from the other direction.

Decide what each one needs

Four outcomes, and most links get the first.

Nothing. The link was ephemeral — a reply in a chat thread from March, already scrolled past. Do not spend effort on these.

Replace with text. The link is in a document or ticket that people still read. The fix is to paste the relevant content in place of the link, from your archive. This is the correct answer for almost everything that matters, because it also removes the dependency permanently.

Replace with a new link on the new account. Available if the new product supports sharing, and worth it only for something long and actively used. Note that you have moved the dependency rather than removed it.

Tell someone. For anything published or embedded where you cannot edit it yourself, the fix is a message to whoever can, before the link breaks rather than after.

Do the text replacement properly

Pasting a whole transcript into a ticket is not usually what the reader needed.

What they needed was the conclusion — the answer, the code, the decision, the list. Take that from your archive, paste it as text, and note where it came from and when. The result is more useful than the link was, and it does not depend on any account continuing to exist.

For long technical material, an attached text file beats an enormous inline paste. Either way it is now in the same system as the thing that referenced it, which is the property you want.

Sequence it before cancellation, not around it

This step goes in the window between the export and the cancellation, and it depends on both.

It needs the verified export, because the replacement text comes from the archive. And it must finish before the account closes, because after that the links are dead and you can no longer see what they pointed at.

Give it a couple of days if there is any chance colleagues are involved. Asking someone to update a page they own is not a same-afternoon operation.

What moves

WHAT MOVES — shared links

  · The conversation content behind a link
                    → moves, into the archive. Available
                      as text to paste anywhere.

  · The links themselves
                    → STAYS BEHIND. They resolve against
                      the old account and stop when it
                      closes.

  · Links in other people's documents
                    → STAYS BEHIND and you cannot see
                      them. Search your sent messages,
                      not the account.

  · Anything published or embedded
                    → STAYS BEHIND unless someone else
                      edits it. Ask before the deadline.

  · Cancelling with links outstanding
                    → IRREVERSIBLE. The links break and
                      you can no longer see what they
                      pointed at to replace it.

Stop creating the dependency

The habit worth changing on the new side: when someone asks for something from a conversation, send the text rather than a link.

A link is convenient for you and a dependency for them, on an account you might close, at a product you might leave. Text in the message or a file attached is slightly more work once and survives everything — including the next switch, which is the one you are not thinking about yet.

Where you do share links, keep a note of who and where. Four lines in a file makes the next round of this ten minutes instead of an archaeology exercise.

What is lost anyway

Anything shared with people you have lost contact with, or pasted somewhere you no longer have access to, or embedded in a system you left a job to get away from. You cannot find those and you cannot fix them, and at some point somebody clicks a dead link and moves on.

That is an acceptable loss and worth naming so it does not become an open-ended search. The links you can find are the links that matter, and finding them takes an hour — as long as the hour happens before the cancellation rather than after.