Productiv is shutting down on August 6. If you're a customer, here's what to do before then and what to do after: what to export today, what to hand off tomorrow, and how to get discovery running again once the platform is offline.
The one thing you can't get back
Everything in your Productiv account falls into one of two buckets: things you can rebuild from systems you still control, and one thing you can't.
Your usage and engagement history is the only unrecoverable asset in your Productiv account. Everything else, inventory, spend, contracts, owners, can be reconstructed after the fact from your identity provider, finance records, and contract files.
Everything rebuildable is a project you can run in October. The usage trend is a door that closes Thursday. That's why it goes first, and why the rest of today is built around it.
Today (August 4): pull the data
Don't start with the app inventory even though it's the biggest list. Start with usage, since it's the one export that can't be recreated by any other system once it's gone.
In this order:
- Usage and engagement history. Longest date range the export tool allows. If it caps the range, run it in chunks and stitch them together, don't accept a shortened window just because the export button offered one.
- Contracts and renewal dates. Filter to anything renewing in the next 90 days and export that set on its own. You'll hand this off separately tomorrow.
- Spend and license counts. Per-app spend, purchased seats, assigned seats, active seats. The gap between assigned and active is your reclamation list for Q4.
- Application inventory, including everything flagged inactive, unsanctioned, or shadow. The unsanctioned list is the one people forget to pull, and it's usually the most valuable part.
- App owners and stakeholders. Rebuilding this by hand later is tedious enough that you'll wish you'd exported it the first time a renewal lands with no owner attached.
- Saved reports and dashboards. Screenshot whatever leadership actually opens. You're capturing the format so you know what to recreate, not the underlying data.
Before you close a single tab, verify what you pulled. Exports truncate silently, and a file that looks complete in the download folder isn't the same as a file that's actually complete.
- Check row counts against what the UI showed you. A CSV that stops at 1,000 rows when your inventory has 1,400 apps looks normal until someone counts it.
- Open every file. Confirm dates came through as dates and not serial numbers, and that currency fields kept their denomination.
- Spot-check the oldest records in the usage export. If it was supposed to cover 24 months, confirm month 24 is actually there.
- Store everything on a shared drive with the export date in the filename, not on your desktop.
Budget an hour for verification. A truncated file discovered on August 7 is functionally the same as never having exported it.
Tomorrow (August 5): hand off, don't sit on it
Your renewal calendar just became a spreadsheet nobody is watching. That's a Finance and Procurement problem as much as it's yours, and it needs to land on their desk today, not after the shutdown.
- Send whoever owns renewals the 90-day extract from yesterday, and get those dates into whatever calendar or ticketing system they actually use.
- Flag auto-renewals with notice periods specifically. A 30-day notice window on a contract renewing in September is something Finance needs visibility on this week.
- Anything with a notice deadline inside the next 60 days, handle manually now. Don't assume replacement tooling will be live in time to catch it.
This is also the day to put two temporary controls in place, because you're about to spend an unknown stretch of time without a system tracking the estate:
- Freeze net-new app purchases that route through expense instead of procurement, or at minimum require a note on them, so you're not discovering three months of unsanctioned spend later.
- Pause automated license true-ups. You don't currently have usage data to validate them against, so let them wait rather than run blind.
Neither control is permanent. Both are cheaper than finding out in November what slipped through in August.
Wednesday onward: rebuild discovery in the right order
Once the deadline passes, the goal shifts from perfect visibility to fast visibility. Sequence still matters:
- Identity provider first. Okta, Entra, Google, whichever you run. One connection recovers most of your sanctioned estate.
- Finance and expense next. This is where the apps that never touched SSO live, the departmental subscriptions on someone's card, the tools procurement never saw. It also catches what your old inventory may have missed entirely.
- Direct integrations for your highest-spend apps, so license counts and usage stay current instead of aging into another stale snapshot.
- Ownership and budgets last, loaded from the owner map you exported Sunday rather than rebuilt from scratch. This is the entire payoff of having exported it.
The faster path back: Zluri's SaaS Management
Zluri is an identity security platform with identity governance at the core, and SaaS Management is one of its products, sitting on the same discovery engine that also powers access reviews and provisioning across the rest of the platform.
That discovery engine is the strong part. It runs across eight independent sources in parallel, SSO, direct integrations, manual entry, transaction and expense data, agents, MDMs, CASBs, and plugins, so the inventory doesn't depend on any single channel catching everything.
In brief, what Zluri's SaaS Management covers:
- Discovery & inventory. Shadow IT gets caught automatically, and every app is classified by authorization status, Managed, Unmanaged, Restricted, or Needs Review, instead of sitting in one undifferentiated list.
- License & contract management. Licenses, Subscriptions, Contracts, and Perpetuals are tracked as distinct commitment types, and the License Mapper auto-maps seats to the users and teams actually holding them.
- Optimization. Waste is split into four categories, Unassigned, Undeprovisioned, Unused, Underused, each pointing to a different fix, and tracked against three separate figures: Potential Savings, Estimated Wastage, and Realized Savings.
- Renewals & notifications. Escalating reminders for renewals, payments, and cancellation deadlines route to the specific accountable owner, not a broadcast list nobody acts on.
- Vendor management. Risk rolls up at the vendor level, across a vendor's full footprint, instead of getting assessed one app at a time.
The part worth sitting with past the immediate scramble: Productiv told you what you had and how it was used, and left access management to manual effort. Reclaiming licenses on a 40%-utilized app still meant a ticket queue. Zluri runs discovery and license reclamation in the same system, so that step is a workflow instead of a separate project.
If August 6 is closing in and you haven't started, talk to us this week. We'll help you through the export and tell you honestly what's recoverable, on Zluri or not.
Frequently asked questions
What's the single most important thing to export?
Usage and engagement history, at the longest date range available. Everything else in your account can be reconstructed from systems you still control. That can't.
My export looks complete. How do I know it actually is?
Compare row counts against what the UI displayed, open every file to confirm it parses, and check that the oldest records in your usage export are actually present rather than silently clipped.
How fast can discovery be running again?
Days, not months, because it connects through systems you already run: your identity provider, finance and expense tooling, and SSO. The identity provider connection alone restores most of the sanctioned estate.
Can Zluri import what I exported from Productiv?
Yes. Inventory, spend, contract, and usage records come in as a starting point, and discovery fills in the rest.
I've already lost access. What now?
Discovery rebuilds inventory, spend, and ownership from your existing systems, so you're not starting from nothing. Historical usage trend is the piece that doesn't come back, which is why it topped today's list.
What should I do about renewals in the next 90 days?
Handle them manually now. Pull the dates into whatever calendar Finance actually uses, and check notice periods individually rather than assuming replacement tooling will be live in time.
.svg)
