Skip down to the research record

Slack export cap: 90 days in GitLab's handbook before close

Quota Forecast Editorial Team · Published · 10 min read

GitLab's handbook says Slack exports of direct messages and private channels cover only the last 90 days. If you run revenue at a small B2B company, a lot of your deal history may live in Slack. Buyers ask questions there, reps agree to terms there, and champions share the real decision criteria there. That makes Slack fast for the team and risky for memory. This post looks at one public example of a Slack export limit, explains what that limit covers and what it leaves out, and offers a simple routine you can run before quarter end.

Key takeaways

  • Under GitLab's policy, Slack exports reach back only 90 days, so find your own export window before you need it.
  • Keep each deal's pricing, commitments and decision makers in a short, dated record that links back to the thread.
  • Use one channel for each account or deal, so discussion among several people stays in one place.
  • Move anything you will need after a few weeks into a document or the deal record.
  • Run a quarter-end routine: name an owner, export while messages are inside the window, and test the export once.

What the GitLab handbook says

GitLab publishes its internal communication rules in its handbook, and two of them matter to anyone who runs deal conversations in Slack. The first is about who can pull data out. According to the GitLab Communication page, the Slack Workspace Owner "has the ability to export data from all direct messages and private channel conversations for the maximum retention period set by GitLab, which is currently set for 90-days."

The second is the hard edge. The same GitLab Communication page says that "All messages that are older than 90-days cannot be exported by the Workspace Owner or any other Team Member at GitLab."

Read together, those two sentences describe a rolling window, not an archive. Anything that moves past the window cannot be pulled out through the export, even by the person who owns the workspace.

Two details are easy to miss. The rule covers direct messages and private channels, which is where a lot of deal talk tends to happen. And it is GitLab's rule for GitLab. This describes GitLab's settings, not yours: your company's Slack plan, settings and admin roles may differ. The practical lesson travels even if the number does not: find out your own export window before you need it, not after.

Why this matters for deals

Deal conversations in Slack are quick and informal. Picture a common sequence, offered as an example rather than a report of any company's history. A buyer's finance contact asks about payment terms in a direct message. Your account executive agrees to a discount in a private channel with the solutions engineer. A champion posts the real decision criteria in a thread that scrolls away within the hour. Weeks later the deal slips, or the rep who ran it leaves, and nobody can say what was promised.

Revenue leaders need that record for three reasons. Forecast reviews depend on knowing what the buyer actually said, not what the rep remembers. Pricing and terms need an audit trail when a deal gets reviewed for approval. And handoffs between reps break down when the history sits in someone's private messages. For what a handoff record should show, see forecast handoff checks.

A thread is not a record. A thread is a conversation, and it is only as durable as the tool that holds it, the people who can open it, and the window that governs it. A record is a short, dated note that someone on the deal team wrote on purpose, with a pointer back to the conversation.

A rolling 90-day window makes that record fragile. If you only learn about the limit when you need the messages, the older ones may already be out of reach. The fix is inexpensive: record the important parts on a routine, well before you need them, rather than trusting that the thread will still be there.

Decide what counts as a deal record

Not every message deserves to be kept. Start by naming what a deal record must hold. For most small B2B teams that list is short:

  • Pricing, discounts and any change to them
  • Scope, dates and commitments made to the buyer
  • Names and roles of the people who make the decision
  • Requests from legal, security or procurement, and how they were answered
  • Anything a future renewal or account manager would need to know

Everything else is conversation. You can let small talk go. Writing this list down also gives your team a test: if a message contains none of these items, it does not need to leave Slack. For more on keeping those records current, see CRM logging habits.

Illustrative example: a deal record layout

A layout like the one below works. Keep it short enough that a rep will fill it in on the same day a call happens.

Deal: [account name] - [product or scope]
Date recorded: [date]
Decision makers: [names and roles]
Commercial terms: [price, discount, payment schedule]
Commitments made to the buyer: [dates, deliverables, named owner]
Open requests from legal, security or procurement: [item, status]
Source: [link to the Slack channel or thread]

The last field, Source, matters. The record should point back to where the conversation happened, so anyone who needs the detail can find it while it is still inside the window. Dated entries help too. A line that says "discount agreed on the call" is weaker than one that gives the date and the people on the call.

Move deal talk into shared channels

The GitLab Communication page also gives a simple recommendation for channels. It says: "If you use Slack and plan to message 3 or more people, we recommend a channel for customer/issue/project/problem/partnership." For a revenue team, that points toward one channel for each account or deal, with discussion that involves several people kept out of direct messages. Name the channel after the account so anyone with access can find it without asking around.

A channel for each deal has a second benefit. When several people need to follow one conversation, it lives in one place, so the record is not split across five private threads. When someone asks "what did we tell them about the timeline," the answer sits in one channel, and one routine can capture it.

Be careful with the threshold. GitLab's rule is a recommendation for when a channel is worth creating, not a rule about how long any channel must last. Your team can set its own cutoff for when a deal channel is open or closed.

Separate short-lived content from durable content

GitLab draws a line between content that is short lived and content that should last. Its handbook page says that short-lived content, such as a one-time report not referred to beyond 2-3 weeks, can remain in a Google Doc or presentation. The point for a revenue team is simple. Chat is fine for the back-and-forth. Anything you will need after a few weeks belongs in a document or the deal record, not only in a thread.

Apply that to deals. A quick question about a logo file can stay in Slack. A pricing summary that a renewal manager will read next year should not stay only in Slack. A signed scope of work, an approval note, or a list of commitments made on a call should land somewhere durable the same day.

Common mistakes to avoid

A few mistakes come up often enough to name.

  • Waiting for quarter end. The export is useful only for messages still inside the window. A review that starts in the last week of the quarter gives the team the least time to fix gaps.
  • Keeping the record in a pinned message. A pinned message still lives in the chat. Put the record where the deal team already works.
  • Assuming someone else owns it. If the admin is the only person who can export, a single absence can stop the routine. Name a backup.
  • Skipping the test. An export nobody has opened is a file nobody can use.
  • Recording opinions as facts. "The buyer seems happy" does not belong in the commercial terms field. Keep the record to what was said or agreed.

A quarter-end recording routine

Build a routine so that no one has to remember it. The steps below are a suggested sequence, not a formal standard.

  1. Name an owner. One person, usually a sales operations lead or the revenue leader, owns the routine. Shared ownership tends to mean no ownership.
  2. Set a regular cadence. A weekly review of open deal channels is enough for most small teams. Pick a day and keep it.
  3. Copy decisions into the deal record. For each open deal, paste the pricing, commitments and decision-maker names into the record your team already uses. Link back to the Slack thread so the context is one click away.
  4. Export what you need while it is inside the window. Ask your Slack admin to export the relevant direct messages and private channels before they age past your retention period. Save the files in a folder that only the deal team can open.
  5. Test the process once. Before quarter end, run a sample export and confirm you can open it and find a known message. A routine you have never tested is a hope, not a control.
  6. Review at quarter end. Walk through open and recently closed deals, check that each has its record, and fill any gaps while the threads still exist.

Step 4 matters most. It is the step that depends on timing, and it is the one most likely to slip when the team is busy. The weekly review works best when the rep closest to each deal brings the notes and a manager checks the record. Keep the meeting short. Each open deal gets a few minutes, and any deal without a record gets an owner and a date.

When a gap is already there

Some deals will already have gaps, especially if a rep is new or the team has never run this routine. Work through them in order.

First, check what the export can still reach. Older messages may already be out of reach, so do not spend hours chasing them. Second, reconstruct only what you can confirm. If a rep remembers a discount but no one can see the message, write it down as a remembered item, with the date you recorded it and the name of the person who remembers. Third, ask the buyer to confirm key commitments in writing, by email, where that fits the relationship. A confirmation sent now is worth more than a recollection built later.

Questions to ask your Slack admin

Before you rely on any plan, put these questions to whoever administers your workspace:

  • Who holds the Workspace Owner role, and who else can export data?
  • Which conversations can be exported, and which cannot?
  • What is our retention period, and is it set by us, by a plan, or by policy?
  • Where do exports go, and who can open them?
  • Has anyone run a test export this year?

The answers tell you whether the routine can work as designed. If the Workspace Owner is away during the last month of the quarter, you need a second person who can export. If the team cannot say where exports are saved, the export is not finished. Write down the answers. If nobody can answer, that is your first finding.

Limits of this example

This is not a claim that Slack deletes messages after 90 days in general, or that every workspace uses a 90-day window. The 90-day figure comes from GitLab's handbook and describes GitLab's own policy. It also does not replace advice from your legal or compliance adviser, who can tell you what records your business must keep and for how long. A revenue team can use GitLab's example to test its own habits. It should not copy the number without checking it against its own settings and obligations.

Start before the window closes

The lesson from GitLab's page is not about one number. It is that a chat history can age out of reach before a deal is finished. Teams that treat the export as a routine, not an emergency, keep their deal records intact through quarter end and through handoffs.

Start this week: name an owner, pick the deal channels, and run one test export. An afternoon of setup now is easier than rebuilding a deal history later.

Frequently asked questions

How far back can a Slack export go?

GitLab's handbook sets the limit at 90 days. Messages older than that cannot be exported by the Workspace Owner or any other team member at GitLab.

Does the 90-day limit apply to every workspace?

No. The 90-day figure is GitLab's own policy, so check your workspace's retention period and who can export before you rely on it.

What belongs in a deal record?

A deal record holds pricing and discounts, commitments made to the buyer, decision-maker names and roles, open requests from legal, security or procurement, and anything a future renewal would need.

Sources