Migrating from Amplitude: From Charts Library to One Timeline

Amplitude is a charts library for behavioral data — hundreds of saved analyses, behavioral cohorts, forecast models. Migrating away only makes sense if you have admitted something first: most of those charts were built once, presented once, and never opened again. What survived is a handful of recurring questions. A migration that ports the questions instead of the charts takes days, not months.

The chart audit

Pull up Amplitude's content usage: which charts and dashboards had viewers in the last 60 days? At most startups the survivors are: an acquisition overview, one or two funnels, a retention curve, and a revenue view someone built with effort. Five questions. Write them as plain sentences — 'where do signups come from', 'how many activate within a week' — because sentences port between tools and charts do not.

Translating the instrumentation

// Amplitude                          // Clycyo
amplitude.track('Signup', props)   →  track('signup', props)
amplitude.setUserId(id)            →  identify(email, props)
identify obj + user properties     →  identify(email, { ...props })
revenue (logRevenueV2)             →  track('subscription_paid',
                                        { revenue, plan }) via webhook

Event taxonomy advice for the new home: collapse Amplitude's Title-Case event sprawl into a dozen snake_case events with properties. 'Button Clicked - Pricing - Header' becomes track('cta_clicked', { page: 'pricing', position: 'header' }) — one event, queryable, naming conventions here.

Where each surviving question lands

• Acquisition overview → automatic: sources, UTMs, landing pages, with first-touch persisted per visitor.
• Funnels → the underlying step events plus drop-off comparison; for the why behind a drop, the per-visitor timeline beats the chart (funnel instrumentation guide).
• Retention → weekly activation-event counts per signup cohort. Less elegant than Amplitude's curves, sufficient for the decision it feeds.
• Revenue → upgraded, frankly: webhook revenue joined to first-touch UTM answers 'which channel pays' — the question Amplitude's session-based lens always answered awkwardly (how the join works).

What does not port — say it out loud

Behavioral cohort algebra, predictive models, and the warehouse-native workflows. If your team runs those weekly with a data person driving, you are Amplitude's actual customer; staying is the right call, as we put plainly in the alternative comparison. The migration is for the teams paying enterprise prices to look at five basic charts — which, by Amplitude's own usage stats, is a large club.

Cutover sequence

1. CSV-export the surviving dashboards for reference; archive raw events via Amplitude's export API.
2. Install the tag, port the dozen events, wire the revenue webhook.
3. Two weeks parallel — expect higher visitor counts cookieless-side — then remove the SDK.

Test the thesis free on the 10k events/month tier: if five sentences cover your real analytics needs, you just saved an enterprise contract.