Smartlook Shutdown: Dates, Exports and Migration

Smartlook's final shutdown is scheduled for 30 September 2027. Check your paid access deadline, save your data, and plan the switch to a replacement.

Reviewed 4 October 2026 against the official Smartlook and Cisco notices and the linked export documentation.

Smartlook has not reached its final platform shutdown. However, new paid sales ended on 31 May 2026, and renewals and subscription expansions ended on 31 August 2026. Existing paid access ends with your subscription term, which can be earlier than the final shutdown.

If you need a replacement now, use our Smartlook alternatives guide. This article covers the retirement dates, historical data and migration sequence.

When is Smartlook shutting down?

The Cisco end-of-life notice sets the sales, renewal and support dates. The Smartlook transition FAQ also gives the later platform shutdown date.

After a paid plan ends, Smartlook describes access through its Free plan until shutdown, subject to that plan's limits. It recommends exporting before your paid subscription expires, and no later than 31 August 2027. Do not treat the final month as a full export or support window.

What can you export from Smartlook?

Separate three jobs: saving reports, preserving the data available through the API, and keeping recordings that you can still play. Completing one does not prove that the others are covered.

Reports and session lists

The Smartlook reporting guide documents reports for dashboards, events, heatmaps and funnels. In the sessions view, it describes a CSV export of up to 1,000 users in a segment. That CSV is a user list; do not assume it is a downloadable archive of every replay.

List the reports your team actually uses. Save the date range, filters and metric definitions with each export, so someone can understand the numbers after the original dashboard is unavailable.

API data

The Smartlook API overview lists visitors, events, funnels and sessions as available resources. It uses project tokens, regional endpoints and paginated results. Its documented request limits differ by plan, so test an export early instead of leaving a large archive until the last day.

Only project owners can manage tokens, according to the token setup guide. Assign an owner for each project, keep tokens out of shared documents, and verify that exported files contain the expected date range and records. Revoke temporary tokens when the export is complete.

Historical replay playback

An API response about a session is not proof that a different product can play its recording. Ask Smartlook support which replay exports your account supports, how long they remain accessible, and whether playback requires Smartlook's service. Then ask your proposed replacement whether it can import that exact format. Test with a real sample before relying on the answer.

Smartlook says historical data will not be automatically migrated into Splunk Digital Experience Analytics. Preserve your own archive and plan the new installation as a separate collection period.

Which Smartlook alternative should you test?

Use the Smartlook alternatives comparison to choose by the work you need to keep: self-hosted website analytics, hosted heatmaps, event-linked replay, native app analysis or Splunk observability. It compares UXWizz, PostHog, Microsoft Clarity, Mouseflow, UXCam and Splunk Digital Experience Analytics, including costs and limits.

Disclosure: we develop UXWizz. It supports website analytics and replay, but it does not record native mobile app screens. Test your actual journey and reports before choosing any replacement.

A practical migration checklist

1. Record your deadlines. Write down the paid plan expiry, export owner and planned cutover date for every project. Leave time to check the archive.
2. Inventory the work you need to preserve. List events, funnels, segments, dashboards, saved investigations and user permissions. Mark what can be exported and what must be rebuilt.
3. Choose a test journey. Use a representative flow such as signup or checkout, including an error case. Run it on the browsers and devices your visitors use.
4. Validate the new collection setup. Check event names, identity rules, masking, consent behavior and retention settings before collecting production traffic. Review any legal requirements with the person responsible for your site's privacy setup.
5. Compare a short overlap period. Check whether important steps appear in both tools. Explain differences caused by sampling, session definitions, consent and time zones instead of expecting identical totals.
6. Finish the handover. Check that exports open, rebuild the reports your team needs, update internal links, and remove the old tracker after the replacement is verified. Store archives with suitable access and deletion controls.

If you are considering UXWizz for a website, use the free trial to test that journey and the replay quality on your own installation. If you need native mobile replay or a fully managed analytics service, start with an option that meets those requirements.