Productiv Deleted Your Data. Here's How to Rebuild Your SaaS Estate From Zero.

Productiv announced its shutdown on August 2, 2026, and named August 6 as the sunset date. Operations did cease on August 6. But customer access to the platform ended on August 5 — a day earlier than announced, which cost some admins their last planned export window.

The data itself is not sitting in cold storage somewhere. Productiv’s site states that “all production systems, data stores, and backups have been permanently and securely destroyed. No customer data has been retained.” As of August 11, no public reason for the shutdown has been given.

One clarification, since the situation has been described loosely elsewhere: this does not appear to be a conventional bankruptcy. Creditor claims are being handled through a third-party administrator, Stretto, at cases.stretto.com/Productiv, with a filing deadline of December 22, 2026 — the kind of structured wind-down that is typically handled outside bankruptcy court. We’re not going to put a firmer label on the mechanism than the public record supports. If you think you have a claim, that deadline is the one to calendar; we’ll cover what the claims process actually looks like for a software buyer in a separate piece.

Worth saying plainly: this was a hard week for the people who built Productiv, not just the people who bought it. A team lost their jobs, and a lot of admins lost a tool they genuinely liked and had staked internal credibility on.

If you’re one of those admins, the export advice everyone published in the first week — including ours — is now useless to you. So here is the version that still works: what’s actually gone, what you can rebuild, and how to get most of it back in 30 days.

What you lost versus what you can rebuild

Be precise about this before you promise anything to your VP, because the two halves have very different timelines.

Gone for good. Historical engagement and utilization trends — the multi-year record of who logged into what, how often, and how that curve moved. In-platform notes, tags, saved views, and workflow configuration. Your license-optimization baselines: the “we reclaimed 340 seats last year” numbers that justified the tool. Any benchmark data that was Productiv’s own, not yours. None of this exists anywhere. There is no backup, no escrow, no partner copy.

Recoverable. Your application inventory. Your annual and monthly software spend. Contract terms, renewal dates, and notice periods. App owners and business sponsors. Purchased license counts. Vendor contacts. All of it lives in systems you still control — your identity provider, your finance stack, your contract repository, your endpoints. Productiv aggregated that data; it did not originate it.

That distinction matters commercially, too. If a vendor offers to “restore” or “recover” your Productiv usage history, they are selling you something that cannot be delivered. The honest offer is help reconstructing the recoverable half faster, and starting a new engagement baseline today.

The four sources that get you to ~90% coverage

This is the core of the work. Four pulls, done in parallel by whoever owns each system, will reconstruct most of a mid-market or enterprise SaaS estate. Assign owners before you start — this stalls when one person tries to do all four.

1. Your identity provider. Okta’s System Log, Entra ID sign-in logs, or the Google Workspace audit log will give you every app users authenticated into, with unique user counts and last-sign-in dates. In Okta, export the app list with assignment counts and pair it with 90 days of sign-in events; in Entra, pull the enterprise applications list plus sign-in logs. This is your fastest path to the sanctioned app list and often takes an afternoon. What it misses: anything not behind SSO. Departmental tools bought on a card, free tiers, tools with local logins, and most of the AI apps that arrived in the last 18 months. Shadow IT is defined by its absence from this list.
2. Your finance systems. Pull 24 months of vendor-level spend from the AP ledger (NetSuite, Coupa, or your ERP) plus corporate card and expense feeds (Ramp, Brex, Expensify). Filter on software and subscription GL codes, but also scan uncoded vendors — that’s where the surprises are. This is your only real source for spend, and your best source for apps IT never knew existed. The obstacle is vendor naming: card descriptors like ADOBE *ACROPRO, resellers and marketplaces (AWS Marketplace, SHI, Insight) that mask the actual product, and parent-brand line items that cover several apps at once. Budget real time for normalization; it’s the least glamorous and most valuable hour of this project.
3. Contracts and email. Your contract repository, DocuSign’s completed-envelope list, and the procurement and AP inboxes together reconstruct renewal dates, term lengths, auto-renewal notice windows, and purchased seat counts. Search the shared drive and inboxes for “order form,” “auto-renew,” “renewal notice,” and “MSA.” What it misses: month-to-month and click-through agreements, which usually have no paper at all and show up only in the finance pull.
4. Endpoint and browser signals. OAuth grants (Google Workspace third-party apps, Entra enterprise app consents), browser extension inventories from your MDM, and installed-application reports from Intune, Jamf, or Kandji. This is the layer that catches free and freemium tools — the AI assistants, the note-takers, the design tools — that never touch finance or SSO. It’s noisy and needs filtering, but it’s the only source that sees them.

Then de-duplicate, and expect it to take longer than you think. The same app will appear in three sources under three names. Normalize on the vendor’s root domain rather than the display name, decide up front whether a suite counts as one app or several, and keep a single alias column so Atlassian, Jira, and JIRA SOFTWARE-ANNUAL collapse to one row. Do this once, deliberately, or you’ll ship an inventory with a 15% inflation rate and lose the room’s trust on the first review.

This four-source pull is what automated discovery does continuously rather than once. If you’d rather not hand-assemble it, Torii connects to those same systems and keeps the inventory current — worth a demo if a manual rebuild isn’t realistic for your team’s bandwidth.

Triage renewals before you finish the inventory

Do not wait for a complete estate map. A renewal inside the next 90 days is money leaving the building while you build a spreadsheet.

As soon as the finance and contract pulls are underway, build a single triage list sorted by next renewal date, with known or estimated annual value in the second column. Work only the next 90 days. For each line, do three things:

Confirm the owner. Not the person who signed it two years ago — the person who will defend the spend this quarter. Unowned renewals auto-renew by default, every time.

Find the notice deadline, not the renewal date. Most enterprise agreements auto-renew unless you give 30, 60, or 90 days’ written notice. The notice date is your real deadline, and for anything renewing in the next 60 days it may already have passed. Check this first; it changes what’s negotiable.

Make the call: renew, renegotiate, or kill. You’ve lost your utilization data, so you can’t argue seat reduction from a Productiv report anymore. You can still argue from purchased-seat counts versus IdP-assigned users, from headcount changes since the last renewal, and from department owners telling you plainly whether their team uses the thing. That’s weaker evidence than you had two weeks ago, and it’s enough to hold a renegotiation.

Two practical notes. Ask each vendor for their own usage numbers — most account teams will share seat activity on request, and for your largest apps that partially backfills what you lost. And if a renewal is genuinely un-triageable in time, a short-term extension at the current rate is almost always available and beats renewing blind for another year.

This list is also the artifact Finance actually wants. Send it to them at the end of week one, unfinished, with the coverage gaps labeled.

Rebuilding an engagement baseline

Your usage history is gone, which means the new clock starts today. Every day you delay instrumentation is a day missing from the dataset you’ll need at the next renewal cycle.

Set this up in week one, not week four. Confirm your IdP is retaining sign-in logs long enough to be useful and export them somewhere durable — default retention in most tenants is far shorter than a renewal cycle, and you will not get those days back. Connect directly to your ten largest apps by spend via API for last-active dates, license tiers, and seat assignments; those ten usually carry most of the negotiating leverage. Turn on SCIM where you can, so provisioning and deprovisioning generate a record instead of a ticket. Keep the endpoint and OAuth telemetry flowing rather than treating it as a one-time pull.

Do that and you’ll have 90 days of real utilization data by mid-November, and a full renewal cycle’s worth by next summer.

This is also the argument against solving the problem with a spreadsheet. A hand-built inventory is accurate on the day you finish it and starts decaying immediately — new tools appear, seats change, someone renews without telling you. Worse, a static inventory can’t produce a utilization trend at all, because trends require continuous collection. The rebuild is a one-time project. The baseline is only worth having if something keeps collecting after the project ends.

What this changed about vendor selection

The obvious lesson is “pick a bigger vendor,” and it’s the wrong one. Company size is a weak predictor, and anyone using this moment to sell you their headcount is selling you a feeling.

The real lesson is narrower and more useful: ask about data egress before you sign, and test it while you’re a happy customer. Three questions belong in every SaaS evaluation from now on:

• Is there a documented, self-serve export of all my objects — inventory, spend, contracts, usage history — not a CSV of the current view?
• Is continued data availability for some defined window after termination a contractual commitment, or a support-ticket favor?
• Can I pull all of it via API on a schedule I control?

Then actually run that export quarterly and put the file somewhere you own. That habit, not vendor selection, is what would have made last week survivable.

We’ll publish the full vendor continuity questionnaire as a follow-up. In the meantime, the thing worth internalizing is that any promise of permanence — including ours — is worth exactly as much as your ability to walk away with your data.

Still comparing platforms? Our Productiv alternatives roundup covers the field.