Yes. The 22-method SOAP API is included with every tier and is available for ongoing data export at any point in your subscription, including during the 90-day cancellation notice window. At cancellation, the published 30-day export window opens — your team has 30 days from the cancellation date to retrieve any remaining data through the API or the standard export tooling. After that window, Evolve data is deleted from production systems within 60 days per the Privacy Policy retention schedule. If you need an extended export window for a complex migration, that's flagged at the time of cancellation notice and handled customer-by-customer.
What you can export
The data you put into Evolve is yours. Export coverage:
Claim records — all fields, status history, financial records, time logs, expense entries, diary notes, photos, documents.
Client and contact records — companies, contacts, customer representatives, default settings, fee schedules.
User records — your team's roster, role assignments, license tracking, branch assignments, authentication metadata. Authentication credentials themselves are managed in AWS Cognito and are not exported in a directly-portable form, but the user-record metadata you'd need to recreate accounts in another system is exportable.
Configuration — fee schedules, claim status types, color coding, alert rules, document categories, template letters, custom report definitions, integration settings.
Reports — historical report runs, custom report definitions, the standard 100+ report catalog can be re-run for archive purposes during your subscription.
TPA records (if you have the TPA Module) — contracts, treaties, reserves, claim shares, authority levels, checkbook records, bordereaux history.
Audit logs — the tamper-evident audit log per claim is exportable in standard formats.
The 22-method SOAP API covers the primary claim, contact, financial, report, and document operations. The REST API in development (Phase 1 Q2 2026, Phase 2 Q3 2026) will sit alongside the SOAP API and add modern HTTP-based export workflows.
During an active subscription
You can export at any time. There's no restriction on how often you query the API or how much data you pull through the standard export tooling. The published per-claim integration fees apply to integration bridges using the bridges in production; standard data export through the SOAP API or the customer-facing export tools doesn't carry a per-claim fee.
During the 90-day cancellation notice
Full export access continues. The platform doesn't downgrade functionality during your notice period — your team uses the system normally, including running exports. Many operations use the 90-day window to systematically export historical data ahead of the cancellation completion date.
After cancellation completes
The published timeline:
Day 0 — cancellation completes (90 days after notice).
Days 0–30 — export window. The platform stays accessible for read-only export. Your team retrieves anything not already pulled.
Days 30–60 — production data deletion. Evolve data is deleted from production systems within 60 days of cancellation completion per the Privacy Policy retention schedule. Backup retention follows the standard backup-rotation schedule and is fully purged in line with the documented retention table.
Day 60+ — data is gone from production and routine backups.
Some categories follow regulatory-driven retention timelines that override deletion (billing records 7 years for accounting purposes, for example). The Privacy Policy carries the retention table by category.
Extended export windows
If your migration is complex enough that 30 days isn't sufficient, flag it at the time of cancellation notice. Extended windows are handled customer-by-customer based on scope and the destination system's import readiness.
What you do not lose at cancellation
Data you've already exported. Anything you pulled through the API or export tools during the subscription or the notice / export windows is yours and stays yours.
Audit trail records you've exported. The tamper-evident audit log records, once exported, retain their integrity off-platform.
The MSA and DPA documentation. The contractual record of what data was processed and under what terms is preserved.
Related questions
Who owns the data my team puts into Evolve?
What's your cancellation policy if Evolve doesn't work out?
What does the contract actually say — what am I agreeing to?
How does Evolve handle claims data privacy and HIPAA-relevant information?
What about Xactimate / XactAnalysis / Symbility / HOVER / TORRENT — does Evolve play nicely with the tools I already use?