Tool
Persana AI
Persana AI shut down in May 2026. Confirm billing and data status, understand its former credits and workflows, and compare Rox, Clay, and Apollo.
Verdict
Do not start a new Persana AI workflow or treat its pricing page as a live offer. Persana's own migration guide says billing stopped on April 1, 2026, access ended after May 1, and the platform was sunset on May 2 while the team joined Rox. Existing customers should reconcile old invoices, contracts, exports, CRM writes, suppression lists, and backups; the export window described by Persana has already passed. Evaluate Rox as a new vendor rather than assuming Persana entitlements, data, credits, or controls carried over.
Persana was a table-based sales prospecting and GTM workflow product. It combined people and company search, waterfall enrichment, AI research, web scraping, buying signals, CRM writes, and outreach handoffs. That product description remains useful when choosing a replacement, but it is historical.
Start with the AI sales tools guide if the replacement category is still open. Compare Clay for configurable enrichment and research workflows, or Apollo when a packaged contact database plus sequences is the priority.
Persana's current status
The Persana migration guide provides the decisive dates: billing was suspended on April 1, customers had access through May 1 to export data, and the platform was scheduled to sunset on May 2. It says all remaining platform data would then be permanently deleted. We did not authenticate to the retired app or independently verify backend deletion, so that last point is the vendor's stated policy, not an audit finding.
Persana's website still exposes a pricing page, feature pages, “get started” links, and trial language. Those remnants conflict with the later shutdown notice. The migration guide controls this review because it is the specific first-party statement about service and billing status. There is no current Persana plan to buy.
| Decision now | What the evidence says | What to do |
|---|---|---|
| New purchase | Billing stopped and subscriptions were canceled | Exclude Persana from a live shortlist |
| Old charges | Persana said no charges would apply after April 1 | Reconcile invoices and contact the address in the migration guide for discrepancies |
| Old data | Vendor said remaining platform data would be deleted after May 1 | Check local exports, CRM history, warehouse copies, consent records, and backups; do not expect the old app to recover data |
| Move to Rox | Persana points customers to Rox People, but says the move was optional | Run a fresh security, data, workflow, and cost evaluation |
| Replace elsewhere | The old workflow joined enrichment, signals, research, and activation | Preserve required outputs and controls before comparing products feature by feature |
What the old product did
Persana's former workflow started with people or company lists, enriched them across external providers, added research and signals, then activated selected records through a CRM, sequencer, Slack, webhooks, or native email. Its waterfall page said operators could order providers, skip enrichment when a verified value already existed, define success rules, and continue to a fallback when a result was missing or unverified.
That shape matters during migration. Inventory each table, source column, formula, prompt, trigger, suppression rule, destination, owner, and failure path. A replacement that can find emails but cannot preserve conditional execution or field provenance is not equivalent. Use CRM enrichment to define safe writes, account research for evidence requirements, and lead scoring for human review gates.
Historical pricing and credit limits
These figures describe the stale Persana pricing page, not purchasable October 2026 plans.
| Former plan | Published price | Published allowance |
|---|---|---|
| Free | $0 | 50 credits |
| Starter | $85 monthly | 2,000 credits/month |
| Growth | $151/month billed annually | 60,000 credits/year |
| Pro | $400/month billed annually | 216,000 credits/year |
| Unlimited | $600/month billed annually | 50,000 credits/month plus some “unlimited” Persana enrichments under fair-use language |
The table priced a found email at one credit and a phone number at ten. It also showed search, export, integration, row, and action-column limits by plan. These terms are useful only for reconstructing an old invoice or estimating the workflow's prior consumption. Persana said active subscriptions were canceled; the published notice establishes no continuing Persana service entitlement for unused credits.
Rox is a separate buying decision. Its current pricing page lists Individual at $100/month for 10,000 Agent Actions, Teams at $255/month for 15,000 actions and unlimited seats, and Enterprise as a quote. Rox says tasks consume different action amounts based on model and processing, monthly allowances refresh, and usage appears in an activity log. Its FAQ still uses older “Starter” and “Core” labels beside cards labeled Individual and Teams. Get the action schedule, renewal behavior, limits, and migration concessions in writing; do not assume Persana credits convert into Rox actions.
Privacy and data boundaries
Persana's public privacy policy is a weak basis for historical customer-data diligence. It names Netla, Inc. but repeatedly refers to “Outboundify,” says it applies only to online website activity, and does not expose a current subprocessor list or product DPA. The linked Notion terms could not be retrieved during our October 11, 2026 checks.
The policy says connected Gmail data was used for sales communication and engagement tracking, encrypted in transit and at rest, retained only as long as necessary, and not used through Google Workspace APIs to train generalized AI or ML models. Those statements do not establish what happened to every enrichment record, prompt, CRM payload, provider result, or backup. Persana separately said remaining platform data would be permanently deleted after May 1. Former customers should retain contractual deletion evidence and map copies held in downstream systems or enrichment providers.
For Rox, start again with its privacy policy, security materials, DPA, subprocessors, connected-system scopes, retention, deletion, AI-provider terms, and outreach controls. A team acquisition and CSV import do not transfer the old privacy assessment.
What historical users reported
G2 reviews describe experiences before the shutdown. In a January 31, 2025 review marked current user, validated reviewer, and organic, Kristi R., a people operations manager, praised hands-on support but reported bulky enrichment lists, missing operational status fields, and product changes that could stop tables or disable features. This is a named historical anecdote, not evidence of current service quality.
We did not use Persana, test provider match rates, verify exports, inspect an old contract, or confirm deletion. The practical decision is still clear: use the archived capabilities as a replacement checklist, treat the live pricing UI as residue, and evaluate any successor on a representative workflow with explicit usage and data terms.
Sources & further reading
- Persana AI platform sunset and migration guide
- Persana AI joins Rox announcement
- Rox announcement about the Persana team
- Historical Persana pricing and credit table
- Historical Persana waterfall-enrichment page
- Persana privacy policy
- Rox People documentation
- Current Rox pricing and Agent Actions
- Current Rox privacy policy
- Historical Persana user reviews on G2
