Hub for teams replacing Adobe Analytics with self-hosted Matomo: retention and extension terms, raw data feeds and Data Warehouse exports, and the migration and cost pages under it.
Adobe Analytics against self-hosted Matomo for enterprise web analytics: reporting depth in Analysis Workspace versus Matomo reports and premium plugins, retention you buy from Adobe versus retention you control, server sizing for high-traffic sites, and which Adobe Experience Cloud dependencies keep teams on Adobe.
Moving from Adobe Analytics to Matomo without a ready-made importer: exporting raw history through data feeds, replaying it into Matomo with the bulk Tracking API, mapping props, eVars and events to Matomo custom dimensions and goals, and switching tags through a tag manager.
Adobe Analytics contract and retention-extension costs against self-hosted Matomo: application and database servers sized by pageviews, premium plugins, implementation and data migration, upgrades and support, and the internal analyst time each option needs.
What Adobe lets you take out before leaving: hourly or daily raw data feeds to cloud storage, Data Warehouse report exports and their delivery limits, the historical raw export Adobe offers before deletion, and the retention deadline that sets the timeline.
For digital teams whose Adobe Analytics use has shifted to product analytics: self-hosted PostHog's event model, funnels, session replay and flags against Adobe's props and eVars, how raw data feeds can seed history, and PostHog's self-hosted limits and lack of vendor support.
Adobe advises Web SDK implementers who may move to Customer Journey Analytics not to lock into the Adobe Analytics schema. This page compares re-implementing for CJA with re-implementing once for self-hosted Matomo or PostHog, including what to export from data feeds before retention runs out.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.