Missed Fetcher's Export? Your 'Not Now' Replies Are Still in Your Inbox

Fetcher shut its platform down on October 16, and the last day to request a full data export closed with it. If you missed that window, it's tempting to write the whole account off before Fetcher deletes what's left after November 19. Don't. The most valuable part of your Fetcher account was never the profile list. It was the replies, and for most teams those are still sitting in their own Gmail or Outlook.

What happened to Fetcher, and what did Juicebox buy?

Fetcher was not acquired. On October 6, 2026, Juicebox agreed to buy Fetcher's "intellectual property and other assets," and the company wound down, so nothing a customer built moves anywhere unless the customer moves it.

That distinction decides what happens to your data. The shutdown FAQ is explicit: "Your candidate data is only shared with Juicebox if you become a Juicebox customer and choose to upload it yourself." Financial terms weren't disclosed.

The scale of what's closing:

• Fetcher was founded in 2016, raised over $30M, and says it served 1,500+ customers and 5,000+ recruiters worldwide.
• Juicebox says 5,000+ companies use it and it has raised $116M, with Sequoia and DST Global among its investors.
• Chris Calmeyn, Fetcher's co-founder and CEO, emailed customers on October 2. David Paffenholz is Juicebox's CEO and co-founder.

One correction for your calendar: Fetcher's FAQ calls the final date "Monday, November 19," but November 19, 2026 is a Thursday. Plan around the Thursday.

Missed the October 16 export? Your replies are probably still in your mailbox

If your team sent sequences through a connected Gmail or Outlook account, every outbound message and every reply lives in that mailbox, not on Fetcher's servers. The exception is teams that used Fetcher's own email-sending service. That history only survives in an export, and replies to it stopped arriving after October 16.

The reason is how Fetcher worked. It sent through your connected mailbox and only tracked replies from people it had contacted. It was a layer reading and writing to your inbox. Switching off the layer doesn't delete the inbox underneath it. HeroHunt's write-up of the shutdown makes this point, and it's the most useful sentence in the coverage.

The test is quick. Search your sent folder for the subject line of a sequence you remember running. If the threads come up with replies attached, you have the asset. If they don't, you were probably on Fetcher's sending service, and your only route is the export request you made by October 16, if you made one. Requests filed by that date will be fulfilled even if the file arrives after shutdown.

Why is the reply history worth more than the profile list?

The profile list is public data that any sourcing tool can rebuild. The reply history is a set of private, dated statements of intent that exist only in your records, and nothing on the open web will give them back to you.

What sequence replies contain:

• Timing replies. "Not now." "Ping me in Q1." The second one carries a date.
• Comp declines. "Comp too low," sometimes with a number attached.
• Opt-outs. "Please don't contact me again."

Each of these tells you something you'd otherwise have to pay for again in time and goodwill. A rediscovered candidate already knows your company, already gave you a reason for saying no, and can get a second message that answers that reason directly.

Gem's 2026 Recruiting Benchmarks Report puts a number on how much this pool now matters, and it names candidates from previous outreach sequences as part of the rediscovered pool.

46%

Your Fetcher replies are part of that pool. The profiles are the cheap part.

Any tool can rebuild who someone is. Only your inbox remembers what they told you.

Of all the replies, the opt-outs matter most. Fetcher's pipeline included candidates who had asked never to be emailed again, and that suppression list can't be rebuilt from public data. A new sourcing tool starts without it. The people who opted out matched your searches before, so they'll match again: same titles, same companies, same skills. Lose the list and your next tool emails them again. People talk, and "they ignored my opt-out" travels further than any employer brand campaign. If only one thing makes it across, make it this list.

How do you rebuild the reply log from Gmail or Outlook?

Search each recruiter's sent mail for your old sequence subject lines, pull every thread that has a reply, and tag each reply by intent. That gets back the asset the export would have held.

1. List your sequence subject lines. Pull them from template docs or from whoever built the sequences. Step two only works if you have these.
2. Search sent mail by subject. In Gmail, in:sent subject:"your subject line" works per sequence. In Outlook, filter Sent Items by subject. Open only threads with more than one message.
3. Log each reply in a sheet. Name, email, date of reply, and the reply copied word for word. Keep the original wording, because your next message will quote it.
4. Tag by intent. Use four tags: timing (with the named date), comp (with the number if given), never contact, and not interested. Add a fifth for bounces and "no longer at this company."
5. Load the never-contact list first. Before anything else goes into a new tool, put the opt-outs in its suppression list.

Do this for every recruiter who ran sequences, including people who have since left. If a departed recruiter's mailbox is still held under your company's retention settings, talk to IT before that account is fully deprovisioned.

How do you re-engage passive candidates who said "ping me in Q1"?

Contact them in November and December, and open by quoting what they told you. A reply that names a date is the warmest record in your pool, and for "Q1" replies that window opens in January. If you reach out first, you're the one they're already expecting.

Before you send, check where each person is now. Some of your "ping me in Q1" people will have moved since they replied, and a message to an old work address, or one that names their old employer, throws away the warmth you're trying to use.

A good re-engagement message does three things:

• Quotes their timing. "You said to check back in Q1, so I'm getting ahead of it."
• Names what changed. A new band, a new team, a different scope. If nothing changed, you're just sending the same pitch again.
• Asks one question. Usually whether the timing still holds.

Sort the rest by how specific the reply was:

The sharper problem is the reqs that were live on October 16. Running sequences stopped mid-flight, so candidates who hadn't reached the later steps never got them. The reqs are still open, the hiring managers are still waiting, and the pipeline that was about to produce a slate has stopped. Rebuilding it from cold is time nobody budgeted for.

How do you revoke the access Fetcher still has?

Revoke it yourself in Google and Microsoft, and delete the ATS API key. Fetcher disconnects on its side, but its FAQ tells customers to "revoke Fetcher's access in your Google or Microsoft account settings, and delete the API key," and until you do, the grant stays live with no one on either side looking after it.

The scope of that grant is the reason to act. Fetcher's Outlook connection requested three permissions:

• Mail.Send, to send as your recruiters.
• Mail.ReadWrite, to read and change their mailboxes.
• offline_access, which is the permission that lets an app keep working in the background until someone revokes it.

A read-write mailbox grant held by a company that is winding down is an access grant with no owner. Treat it like offboarding an employee:

1. Google Workspace admin. Open API controls, then third-party app access. Remove Fetcher, and also remove Nylas, the Google Calendar middleware Fetcher's setup asked admins to approve. Revoking one doesn't revoke the other.
2. Individual Google accounts. Have each recruiter check their own third-party connections for anything they authorized personally.
3. Microsoft Entra. Find Fetcher under enterprise applications, remove it, and review the consents granted to it.
4. ATS. Delete the API key you issued to Fetcher.

Order doesn't matter for your reply recovery. Revoking Fetcher's access doesn't touch the mail in your mailbox, so you can lock things down today and search sent mail tomorrow.

How should you pick a Fetcher alternative without letting Nov 19 decide?

Pick on what the tool does at the tier you'll actually pay for, not on the deadline. Juicebox's Fetcher offer runs through November 19, the same day your remaining data is deleted, and having both on one date pushes teams toward a rushed decision.

Juicebox is the obvious landing spot, given the Juicebox Fetcher acquisition. Its entry price is $99 on annual billing or $119 on monthly billing, but ATS integration is only on the Business plan. If you came from Fetcher, where ATS sync was part of how you worked, price the tier that includes it.

Whatever you choose, ask four questions:

• Does ATS sync come at the price you were quoted?
• Can you import a suppression list before the first send?
• Does it send through your own mailbox, so the reply history stays yours next time a vendor shuts down?
• Can you export replies and reply status, not just profiles?

The last two questions are the real lesson from the Fetcher shutdown. Profiles can always be found again. What you can't replace is the record of what people told you, so keep it in systems you own.

FAQ

Can I still get a Fetcher data export?

Not a new one. October 16 was the last day to request a full export, and requests made by then will be fulfilled even if the file arrives after shutdown. After that, email support runs until November 19. If you sent through a connected Gmail or Outlook account, your best source is your own sent mail, which holds both the sequences and the replies.

Does my Fetcher data transfer to Juicebox?

No. Juicebox bought Fetcher's intellectual property and other assets, not the company or its customer accounts. Your candidate data only reaches Juicebox if you become a Juicebox customer and upload it yourself.

What happens to Fetcher account data after November 19?

Fetcher says it will securely delete all remaining account data. Its FAQ calls the date "Monday, November 19," but November 19, 2026 is a Thursday, so treat Thursday as the real deadline for anything you still need from support.

Do I need to revoke Fetcher's access if the platform is already offline?

Yes. Fetcher disconnects on its side but asks customers to revoke access themselves. Remove Fetcher and Nylas in Google Workspace, remove Fetcher from Microsoft Entra enterprise applications, and delete the ATS API key. A Mail.ReadWrite grant with offline_access stays valid until someone revokes it.