A small product group working through papers at a long table
Fig. 01 — Working table, not a vendor demo. Penang and remote.
Legacy app teams · Penang

Keep Monday’s figures when the app itself changes address.

We write the measurement baseline before you retire a wrapper, a native client, or an ageing hybrid — so the destination build is asked to honour the reports you already defend.

Request a baseline review
Who this is for

You still ship the old client, and a freeze date is on the wall.

  1. 01 Product owners who must explain last year’s Ramadan or 11.11 figures after a rewrite, and do not want those charts invented in a spreadsheet.
  2. 02 Analytics leads who can already see that the destination SDK will mint new identifiers, and need that fact in writing before engineering locks tickets.
  3. 03 Release managers who have lived through a store switch where session counts fell off a cliff and nobody could say whether the app or the instrumentation had changed.
Flagship engagement

Pre-migration Analytics Baseline

A written inventory of what your current app actually records, which figures will go dark at cutover, and what the destination build must capture before the old version is retired.

Most of the work is reconstruction: clicking the live app, reading the property you already have, and sitting with the person who currently explains the weekly pack. The artefact is a brief, not a hosted product.

Read the full engagement

Two colleagues comparing notes across a table
Intake is a conversation about the reports you refuse to lose, not a software tour.
Also in the practice

Work that sits around the freeze.

All engagements
Colleagues at a table reviewing papers during a release-week meeting
Release window

Cutover Continuity Review

A timed check in the weeks around freeze: whether the destination build actually emits the events the baseline named, and which charts will need a footnote on the week you switch stores.

Engagement notes
Lined notebook and printed sheets used to list screen names and events
Naming work

Event Taxonomy Mapping

A mapping from the names your legacy app already uses — screen titles, event strings, user properties — onto the vocabulary the destination SDK and the receiving property will accept.

Engagement notes
Two people comparing printed reports at an office table
After the switch

Post-move Reconciliation

A comparison of the first complete reporting period on the new build against the baseline, with a short list of missing events, double counts, and figures that should not be charted year-on-year yet.

Engagement notes
Small group working with notes on a table during a facilitated session
Half-day in the room

Team Working Sessions

A facilitated half-day with product, engineering, and whoever currently owns the weekly numbers, used to agree what must be instrumented before freeze rather than to present a slide deck.

Engagement notes

They sat with our Android lead and clicked the live wrapper, not the Figma file. Eleven screens we still ship were silent in the property.

Priya Nair, product owner — Pre-migration Analytics Baseline

More from the room

From the practice

Notes on cutover, screens, and stubborn charts.

All notes
A person holding a phone, the kind of device a legacy app still lives on
2026-03-12 · Lina Tan

What actually goes dark the week you leave a legacy app

Store downloads keep arriving. Almost everything else — funnels, retention cohorts, even the meaning of a session — can fail silently if the destination build was instrumented from a vendor template.

Read the note
Open notebook and papers on a desk used to reconcile two reporting periods
2026-01-21 · Hafiz Rahman

Keeping a year-on-year chart honest after the app changes address

A cutover is a break in the series. You can still talk about the business, but you should stop pretending the line is continuous unless the identifiers and the event names survived.

Read the note
Patani Road

Write with the app name and the freeze you are protecting.

We reply within two working days. If the window is already too tight for a full baseline, we will say so and suggest a cutover note instead.

Open a scoping note

Room at 130E,Patani Road,Kampung Rawa,10150,Malaysia

Telephone +6042831831

info@platform-pulsehub.digital