01Why you have to export before March 31, 2027
Retrace data stays behind unless you download it yourself.
BMC Helix, which owns Stackify, ends Stackify Retrace on March 31, 2027. Retrace is SaaS-only, so after that date nobody can log in, send data or open stored data. BMC's end-of-life letter says customers are responsible for exporting anything they want to keep before then.
There is no automatic migration either. BMC says there is no automated conversion from Retrace to OpenTelemetry or to any other platform. Your logs, dashboards and alert history do not follow you to the next tool.
Until the deadline, Retrace keeps running in maintenance mode. It gets no new features, only fixes for high-impact issues and security updates. Stackify support stays available at support@stackify.com until March 31, 2027.
For the full timeline and your options, see Stackify Retrace end of life: what to do.
02What Retrace lets you export
BMC's end-of-life guidance points to logs and custom dashboards. Retrace can also export APM summary data.
Logs: app logs, syslogs, access logs and event logs from the Retrace Logs Dashboard, downloaded as files.
Custom dashboards: emailed as a PDF snapshot of the widgets for the time range you pick.
APM summary data: Stackify added CSV export of APM summary data, such as the request, SQL query and web service lists, in 2019.
Everything else: individual traces, error details, monitors, alert rules and app settings have no documented export. Write down the parts you rely on (see the checklist below) so you can rebuild them in your next tool.
03Export logs from the Retrace Logs Dashboard
Three steps, from Stackify’s "Exporting Logs" guide.
Step 1: Turn on log export in Settings > Account Settings.
Step 2: Open the Retrace Logs Dashboard and apply the filters and fields for the slice you want, such as one app, one environment and one time range. The export keeps whatever filters are applied.
Step 3: Click Export. Your browser downloads a zip with a Readme.md and a .log file, in the same format the dashboard showed.
If the download fails in the browser, Retrace also emails you a link to try again. You may have to log in again to use it.
04Plan around the export limits
Large histories need many small exports.
Each export is capped at 100,000 log entries or 50 MB, whichever comes first. Exports are on demand only: Stackify lists scheduled exports as a future feature.
A large log history therefore means many small exports. Split them by app and by time range, keep a simple list of what you have downloaded, and check it for gaps before the deadline.
Start with what you are required to keep, such as the log ranges your audits or contracts ask for, and the time windows of past incidents you may need to review again.
Exported files open without any login, so store them like any other sensitive data.
05Save dashboards as PDF reports
A PDF snapshot is the only documented way to keep a dashboard.
Open a custom dashboard, pick the time range and email it as a report. Retrace sends a PDF with all the widget data for that range. Repeat it for each period you want to keep, for example one report per quarter.
Public read-only dashboard links are not an archive. They stop working when Retrace shuts down.
06Write down the settings you will rebuild
Retrace has no documented export for these, so record them by hand.
Alert rules: the condition, threshold, time window and who gets notified for each alert you actually use.
Monitors: the URLs, servers and metrics you watch, with their warning and critical levels.
Apps and servers: a list of every app, its language and runtime, where it runs and who owns it.
Dashboards: the widgets each team looks at during an incident, so you can recreate the important views first.
Integrations: where alerts go today, such as email, Slack or a paging tool.
07Keep the exports somewhere you control
Put the zip files and PDFs in storage your company already manages and backs up, such as a shared drive or a cloud storage bucket with access limited to the people who need it.
Name each file by app and date range so anyone can find the right one during an audit, and note who exported it and when.
08Start building history in your next tool now
Exports keep the past. Your next tool only knows what happened after you install it.
A new monitoring tool has no history on day one, so install it well before Retrace switches off. Run it next to Retrace and by the deadline you will already know what normal latency, error rates and slow queries look like in the new tool.
With Atatus, start with the .NET migration guide if you run .NET, the guide to replacing Retrace agents in Java, PHP, Node.js, Python and Ruby, or the OpenTelemetry route. Logs go to Atatus Log Management, and you can archive logs to your own S3 bucket for long-term retention.
Comparing tools first? See Atatus as a Stackify alternative or the general guide to migrating from Stackify to Atatus.