Last updated: November 2026
Key Takeaways
- Key finding: Amplitude is a product analytics engine, and Google Analytics 4 is an acquisition and attribution platform. Neither tool covers the other’s job.
- Schema: Standard GA4 is a flat key-value model with 25 custom parameters per event. Amplitude is a nested JSON model with no 25-parameter cap.
- Identity: Amplitude is a deterministic three-tier graph with retroactive stitching. GA4 is a four-tier Reporting Identity model that withholds data on small segments.
- Cost: Standard GA4 is free but capped at 14 months of retention. GA4 360 starts at $50,000 annually, and Amplitude Starter includes 50,000 MTUs.
- Warehouse: GA4 exports to BigQuery with a 1,000,000-event daily streaming cap. Amplitude offers Snowflake zero-copy sharing and warehouse-native queries.
- Decision: Enterprises above 50,000 monthly active users run both engines through one server-side telemetry layer, which removes duplicate instrumentation.
Dated Primary Tracker. Where each platform and layer stands as of November 2026, with the section of this guide that carries the detail.
| Entity | Category | Status | Key Metric | Primary Source | Last Verified |
|---|---|---|---|---|---|
| Amplitude | Product analytics | Recommended for in-product behavior | Nested JSON properties, no 25-parameter cap | e-CENS client deployments | November 2026 |
| Google Analytics 4 | Acquisition analytics | Recommended for paid media attribution | 25 custom parameters per event, 14-month retention | e-CENS client deployments | November 2026 |
| Google Analytics 360 | Enterprise GA4 tier | Upgrade path for sampling and retention | $50,000 annually, 100 parameters, 50-month retention | This guide: TCO teardown | November 2026 |
| Amplitude Starter | Entry pricing tier | Free starting point for small teams | 50,000 monthly tracked users | e-CENS client deployments | November 2026 |
| BigQuery export | GA4 warehouse export | Required for un-sampled deep analysis | 1,000,000 events daily streaming cap | e-CENS: customer data platform | November 2026 |
| Server-side tagging | Shared ingestion layer | Required for dual-stack parity | One payload routed to both engines | e-CENS: server-side tagging | November 2026 |
Enterprise teams face one architecture decision: standardize on Google Analytics 4, commit to Amplitude, or run both platforms in one synchronized stack. Marketing teams need multi-touch attribution, ad campaign return on investment, and tight integration with the Google marketing ecosystem. Product, growth, and retention teams need unconstrained path analysis, instant cohort generation, and flexible event properties.
Amplitude and Google Analytics 4 are not substitutes. Google Analytics 4 is an acquisition and marketing attribution platform built around sessions and traffic provenance. Amplitude is a behavioral analytics engine built to dissect user journeys inside applications and logged-in environments. Forcing either platform to do the other job creates blind spots and engineering overhead.

Modern enterprise growth needs two answers. Which campaigns acquire high-value customers efficiently, and how do those users move, hit friction, and find value inside the product? A sound evaluation covers data modeling, identity resolution, query velocity, warehouse interoperability, compliance posture, and total cost of ownership.
Which Platform Wins for Enterprise Growth: Amplitude or Google Analytics 4?
Amplitude and Google Analytics 4 split the customer lifecycle between them, and neither platform covers it alone. Amplitude is the stronger engine for in-product behavioral work, and Google Analytics 4 is the benchmark for cross-channel acquisition attribution.
Amplitude ingests nested event dictionaries and returns sub-minute query latency. Amplitude cohorts recalculate dynamically across un-sampled monthly tracked users. The GA4 limits are 25 custom dimensions per event, processing delays up to 48 hours, and sampling on ad-hoc explorations above 10 million events.
Marketing teams on Amplitude alone give up native Google Ads Smart Bidding integration. Product teams on Google Analytics 4 alone hit visibility gaps in multi-step onboarding flows. Enterprises must allocate GA4 to paid acquisition governance and Amplitude to product activation and retention.
Digital architectures scaling beyond 50,000 monthly active users should run both engines through unified server-side telemetry, which removes instrumentation duplication.
How Do Amplitude and Google Analytics 4 Differ in Architecture?
The architecture differs below the surface, and the sales narrative is a poor guide. Google Analytics 4 is an event model that replaced Universal Analytics session counts, and it stays tied to the Google advertising ecosystem through aggregate conversion modeling. Amplitude is a raw event stream processor with user-centric behavioral sequencing and direct in-app experimentation.
The dated comparison below tracks the core architectural capabilities of both platforms across the enterprise dimensions we verified in client deployments:
| Feature / Capability | Amplitude Architecture | Google Analytics 4 Architecture | Strategic Advantage | Target Enterprise Profile | Last Verified Date |
|---|---|---|---|---|---|
| Event Data Model | Nested JSON dictionaries supporting dynamic property arrays without manual pre-registration. | Flat key-value schema limited to 25 custom parameters in standard properties and 100 in 360. | Amplitude provides superior flexibility for modeling multi-state interactions directly in the UI. | Product-Led Growth SaaS, FinTech, and Mobile Applications | October 2026 |
| Identity Resolution | Three-tier hierarchy (Device ID, User ID, Amplitude ID) with server-side aliasing and retroactive stitching. | Four-tier reporting identity (User-ID, Google Signals, Device ID, Modeled Data) with thresholding. | Amplitude delivers deterministic user tracking; GA4 enables probabilistic cross-device modeling. | Omnichannel Retailers and Cross-Platform SaaS Platforms | October 2026 |
| Query Engine & Latency | Proprietary columnar database (Nova) delivering sub-minute queries across un-sampled events. | Dual processing pipeline: streaming buffer coupled with batch processing up to 48-hour latency. | Amplitude enables immediate exploratory analysis; GA4 requires BigQuery export for rapid queries. | Enterprise Growth Teams and Product Operations | October 2026 |
| Ad Ecosystem Integration | API-driven cohort syncing to third-party ad networks including Google Ads, Meta, and DSPs. | Native bidirectional linking with Google Ads, Search Ads 360, Display & Video 360, and Merchant Center. | GA4 offers unmatched bidding optimization and audience synchronization within Google stack. | Performance Marketing Agencies and Paid Media Teams | October 2026 |
| Behavioral Funnels & Paths | Multi-path conversion funnels with exact step ordering, exclusions, windows, and Pathfinder flows. | Funnel Exploration reports with strict sequential constraints, limited steps, and session boundaries. | Amplitude visualizes emergent drop-off paths and non-linear discovery without upfront definitions. | Product Management and UX Research Teams | October 2026 |
| Warehouse Lakehouse Sync | Native zero-copy data sharing and streaming with Snowflake, Databricks, BigQuery, and AWS S3. | Direct native streaming and daily batch export to Google Cloud BigQuery with raw nested tables. | GA4 integrates into Google Cloud; Amplitude excels across multi-cloud enterprise lakehouses. | Enterprise Data Engineering and Lakehouse Architects | October 2026 |
| In-App Personalization | Integrated Guides, Surveys, Feature Flags, and Experimentation engine linked to behavioral cohorts. | Requires external third-party testing tools, custom Tag Manager triggers, or web testing platforms. | Amplitude enables immediate closed-loop optimization directly from insights in a single interface. | Digital Product Optimization and Growth Teams | October 2026 |
| Data Governance Tools | Amplitude Data provides schema contracts, linting, tracking plan versioning, and anomaly blocking. | Basic event creation rules inside admin interface; lacks native schema validation pipelines. | Amplitude prevents tracking schema degradation before invalid data corrupts production reporting. | Enterprise Analytics Engineers and Data Governance Officers | October 2026 |
| Regulatory Compliance | Operates as a first-party data processor; provides EU residency and signs HIPAA BAAs. | Operates within Google ad infrastructure; does not sign HIPAA BAAs; subject to transfer scrutiny. | Amplitude offers superior legal safety and compliance isolation for regulated sectors. | Healthcare, Telemedicine, Banking, and Global Enterprises | October 2026 |
| Commercial Licensing | Free Starter tier up to 50,000 MTUs; Plus, Growth, and Enterprise tiers priced on active users. | Free standard tier with cardinality limits; Analytics 360 enterprise tier starting at $50,000 annually. | GA4 standard provides free basic web tracking; Amplitude offers scalable pricing aligned to users. | All Enterprise Tiers evaluating Total Cost of Ownership | October 2026 |
What Are the Data Model and Ingestion Limits in Amplitude vs. GA4?
Data schema is the primary technical distinction between Amplitude and Google Analytics 4. Both platforms are event-based, and the architectures diverge on rich contextual metadata. For technical architects, that divergence decides whether teams run self-serve exploration or wait on data engineers to write SQL.
Google Analytics 4 is a flat key-value schema. Standard GA4 allows 25 custom parameters per event. Text values are capped at 100 characters, and numeric fields follow strict formatting rules. GA4 360 raises the limit to 100 parameters, and the structure stays flat.
Parameters stay invisible in standard reports and Explorations until an administrator registers them as Custom Dimensions or Metrics. Unregistered parameters reach BigQuery exports but remain unavailable inside the reporting interface.
Amplitude is a flexible property dictionary built on nested JSON objects. Engineering teams pass complex metadata in one dispatch, including product feature arrays, permission hierarchies, and multi-state session dictionaries. The Amplitude model has no 25-parameter cap. Every property in the payload is indexed on arrival, so it is searchable, filterable, and segmentable in the interface without administrative pre-registration.

Development velocity is the first operational cost. Amplitude surfaces newly tracked properties immediately to product teams. In GA4, an analyst must configure custom definitions, watch quota use, and avoid the 50-dimension cap on standard properties. Exceeding the limit means dropped parameters and permanent blind spots.
Operational governance points to server-side tagging. A server-side container captures client-side events once, runs real-time schema validation, and routes standardized payloads to Amplitude and GA4 without a performance penalty.
How Do Amplitude and GA4 Resolve User Identity Across Devices?
Identity resolution is the second structural difference. A unified customer view needs connection across devices, browsers, and mobile operating systems. Amplitude is a deterministic user graph. Google Analytics 4 is a probabilistic, modeled aggregation.
The Amplitude identity hierarchy is deterministic and three-tier: Device ID, User ID, and Amplitude ID. Unauthenticated visitors receive an anonymous Device ID. On authentication, the client application sends a deterministic User ID, such as an internal customer database key. Server-side aliasing maps the Device ID to the authenticated User ID.
Retroactive session stitching is the Amplitude advantage. An anonymous user browses documentation, uses calculators, and inspects product tiers for weeks before creating an account. Amplitude unifies those historical anonymous interactions under the authenticated profile. Product teams then inspect the chronological journey before registration and identify the behavioral drivers of conversion.
Google Analytics 4 unifies identities through Reporting Identity, which evaluates four tiers: User-ID, Google Signals, Device ID, and Modeled Data. The hybrid model creates three operational challenges:
- Data Thresholding: GA4 enforces privacy thresholding when Google Signals connects cross-device actions through signed-in users. Segments with small user volumes are withheld entirely, so analysts cannot inspect niche, high-value enterprise accounts.
- Lack of Retroactive Stitching: Standard GA4 does not merge prior unauthenticated sessions to a User ID once registration occurs. Historical touchpoints stay tethered to the anonymous client ID, and the pre-conversion journey stays obscured.
- Consent Mode Modeling: Under European privacy rules, GA4 uses behavioral modeling to approximate unconsented visits. Modeled data supports traffic totals but cannot build granular behavioral cohorts or deterministic profiles.
For B2B software and digital subscription businesses, Amplitude deterministic aliasing is the sequence tracking that self-serve customer funnels require.
Which Platform Wins for Product Behavior vs. Marketing Attribution?
The functional split follows the analytical mandate: product lifecycle optimization for Amplitude, paid media acquisition governance for Google Analytics 4.
Google Analytics 4 is purpose-built for acquisition attribution. Marketing departments spread budget across search, programmatic, social, and affiliate channels, and they need precise performance reporting. GA4 offers multi-touch attribution models, including Data-Driven Attribution (DDA), first-click, last-click, and linear distribution. Return on ad spend and media acquisition sequences are calculated inside standard reports.
GA4 is the operational bidding engine for Google advertising platforms. Conversion signals from GA4 stream into Google Ads, Search Ads 360, and Display & Video 360 to train Smart Bidding algorithms. Replacing GA4 in that role degrades campaign optimization, disconnects Google click identifiers (GCLID), and starves bidding systems of statistical inputs.
In-product exploration is where GA4 falls short. Multi-step onboarding funnels with dynamic time windows, property exclusions, or branching workflows expose rigid interface constraints in GA4 Explorations. GA4 funnels enforce strict linear ordering and struggle with branching paths common in digital products.
Amplitude carries dedicated behavioral exploration tools for product teams:
- Pathfinder & Journey Mapping: Amplitude Pathfinder visualizes all inbound and outbound pathways from any chosen event. Teams uncover navigation loops, unintended exits, and emergent user behaviors without defining rigid funnels first.
- Compass Correlation Engine: Amplitude Compass analyzes tracked behaviors against target outcomes such as Day-30 retention. The engine computes statistical correlation coefficients and exposes the feature interaction that acts as an activation threshold.
- Dynamic Behavioral Cohorts: Amplitude builds cohorts from interaction frequency, sequencing, and properties over rolling windows. Cohorts refresh dynamically in real time.
- Retention Analysis: Amplitude plots bracketed, unbounded, and return retention curves. The curves show whether a feature release improves or degrades stickiness across daily, weekly, or monthly intervals.
Executing advanced analytics across the enterprise starts with one fact: acquisition and product retention are interdependent. Ad clicks without product retention produce subscriber churn. Product metrics without attribution data stop growth teams from scaling acquisition channels.
How Do Amplitude and GA4 Stream Data Into a Lakehouse?
Lakehouse streaming is the integration layer where both platforms have to land raw event data. Enterprise data architectures put that telemetry in a central cloud warehouse, including Snowflake, BigQuery, Databricks, and Amazon Redshift. Neither tool is an isolated silo.
Google Analytics 4 exports raw events to Google Cloud BigQuery. The GA4 BigQuery datasets bring three operational hurdles:
- Nested Record Schemas: GA4 stores event parameters in a nested record array called
event_params. Extracting a single parameter needs SQL with multipleUNNEST()operations, which drives up query compute cost and complicates dashboards. - Streaming Export Limits: Standard GA4 caps streaming BigQuery exports at 1,000,000 events daily. High-volume sites hit that ceiling fast, and avoiding truncation means Analytics 360 or a custom ingestion pipeline.
- Table Partitioning Overhead: Daily exports land in date-partitioned tables (
events_YYYYMMDD), and intraday streaming data lands in temporary tables. Data engineers must deduplicate and reconcile the tables daily.
Amplitude is an open data sharing architecture for multi-cloud deployments:
- Snowflake Zero-Copy Data Sharing: For Snowflake environments, Amplitude provides secure data sharing. Raw event streams appear directly in client accounts with no pipeline maintenance, extraction tasks, or file egress charges.
- Warehouse-Native Analytics: Amplitude queries event records directly inside Snowflake or BigQuery, which separates the visualization interface from cloud storage.
- Bidirectional Synchronization: Amplitude ingests computed attributes from the warehouse. Customer scores, contract values, and offline lifecycle statuses from the lakehouse enrich Amplitude profiles for real-time segmentation.
A unified customer data platform framework keeps the warehouse as the single source of truth, aligning marketing acquisition data with product lifetime engagement.
What Is the Total Cost of Ownership for Amplitude vs. GA4?
Total Cost of Ownership (TCO) is the right comparison, not baseline software price. The TCO calculation covers licensing fees, cloud compute, and the engineering hours that keep tracking pipelines alive.

Google Analytics 4 is free at the standard tier, and Google Analytics 360 is the enterprise tier. Standard GA4 carries zero license cost and four constraints: API quotas, sampling on explorations above 10 million events, a 14-month data retention cap, and a 1,000,000-event daily BigQuery streaming limit.
Bypassing those limits means extensive BigQuery data engineering or an upgrade to GA4 360, which starts at $50,000 annually. GA4 360 raises parameters to 100, removes exploratory sampling up to one billion events, and extends retention to 50 months.
Amplitude prices commercial plans on Monthly Tracked Users (MTUs) or event tiers. The Starter plan is 50,000 MTUs with core analytics charts at no cost. Scaled organizations move to Plus, Growth, or Enterprise plans:
- User-Centric Predictability: Pricing on active users lets product teams capture granular behavioral telemetry without billing penalties for event spikes.
- Integrated Platform Modules: Amplitude bundles A/B testing (Experiment), user surveys and guides (Guides), and Session Replay in one ecosystem, which removes separate software licenses.
- Decreased Engineering Overhead: Product managers and analysts build funnels and cohorts in the Amplitude self-serve interface, so data engineers spend fewer hours on manual reporting requests.
A complete TCO review covers software contracts, cloud compute, and engineering salaries. For digital product enterprises, Amplitude often lowers total operational cost by unifying behavioral analytics, feature flagging, and onboarding interventions in one environment.
What Is the e-CENS Dual-Stack Analytics Matrix (DSAM-4)?
The e-CENS Dual-Stack Analytics Matrix (DSAM-4) is the alternative to an artificial platform choice. DSAM-4 is an enterprise framework that coordinates marketing attribution and product behavioral intelligence in one non-redundant system.
The DSAM-4 model splits the digital analytics architecture into four operational layers:
How Does Layer 1 Unify Telemetry and Server-Side Ingestion?
Layer 1 is single-tag telemetry managed through server-side Google Tag Manager or a customer data pipeline. Client applications send vendor-agnostic payloads to a private cloud endpoint, which normalizes schemas and routes identical event records to Amplitude and GA4 at once. That design protects site speed and keeps raw inputs consistent.
How Does Layer 2 Harmonize Schemas and Identity?
Layer 2 is schema harmonization and identity governance. A dual-stack deployment needs shared event definitions across marketing and product squads. The layer sets a unified tracking dictionary enforced by data contracts, and teams align event naming rules and customer identifiers across both systems. A structured measurement strategy keeps conversion counts and customer IDs matched across GA4 acquisition reports and Amplitude behavioral funnels.
How Does Layer 3 Connect the Lakehouse?
Layer 3 is lakehouse interoperability, and both tools feed raw event records into the central enterprise cloud data warehouse. GA4 delivers campaign attribution parameters to BigQuery, and Amplitude streams detailed product interaction logs into Snowflake or BigQuery. Automated transformation pipelines in the warehouse join top-of-funnel acquisition sources with product retention metrics, which produces holistic customer lifetime value intelligence.
How Does Layer 4 Close the Activation Loop?
Layer 4 is closed-loop activation, where analytical insight becomes commercial action. Amplitude exports dynamic behavioral cohorts into Google Ads and Display & Video 360 for re-engagement and lookalike expansion. Acquisition source data from GA4 informs in-app onboarding personalization, so product walkthroughs match the campaign that started the visit.
When Should an Enterprise Use Both Platforms?
The allocation of responsibilities between Amplitude and GA4 is a function of business model:
Scenario 1: Enterprise B2B SaaS and Product-Led Growth
A B2B SaaS vendor drives inbound trials through search ads, content assets, and partner campaigns. GA4 tracks top-of-funnel campaigns and optimizes Google Ads bidding. After registration, Amplitude runs product tracking for workspace setup, feature adoption, and seat invites. At defined activation milestones, Amplitude alerts sales teams through CRM webhooks and opens expansion conversations.
Scenario 2: Omnichannel Retail and E-Commerce
An omnichannel retailer runs web storefronts, native mobile apps, and physical points of sale. GA4 handles multi-channel campaign attribution and Google Shopping bid automation. Amplitude tracks checkout funnels and mobile apps, diagnoses checkout friction, measures product recommendation engagement, and follows loyalty adoption. Churned shopper cohorts move from Amplitude to Google Ads for retargeting.
Scenario 3: FinTech, Neobanking, and Regulated Financial Services
A FinTech digital banking platform balances compliance obligations against customer acquisition. GA4 is confined to unauthenticated public marketing pages, which keeps financial transactions out of ad networks. Amplitude tracks authenticated web and mobile banking workflows under an executed Business Associate Agreement and European Union cloud residency, analyzing loan completion funnels and feature retention under strict privacy controls.
Scenario 4: High-Traffic Media, Streaming, and Digital Publishing
A media network monetizes programmatic ads and paid subscriptions. GA4 tracks aggregate readership, syndication sources, and ad impressions across anonymous visitors. Amplitude evaluates subscriber retention, video completion rates, and paywall conversion funnels. The division gives editorial teams reach insight and subscription teams revenue insight.
How Do Amplitude and GA4 Handle Compliance and Data Governance?
Analytics architecture is a compliance decision. Regulators enforce standards on cross-border data transfers, consumer privacy consent, and the separation of analytical tracking from commercial advertising systems.
Google Analytics 4 sits inside Google commercial infrastructure. Telemetry connects to advertising systems, so GA4 faces European scrutiny over transatlantic data transfers under GDPR. Google does not sign HIPAA Business Associate Agreements (BAAs), which makes GA4 non-compliant for Protected Health Information (PHI).
Amplitude is a dedicated first-party software data processor. Amplitude provides dedicated European Union cloud hosting on Amazon Web Services in Frankfurt, so event data stays inside European boundaries. Amplitude executes HIPAA BAAs, holds SOC 2 Type II and ISO 27001 certifications, and provides automated deletion APIs for GDPR and CCPA requests.
Schema governance is the control that keeps tracking accurate. Without validation rules, enterprise analytics collect naming discrepancies and duplicate events. Amplitude Data provides native tracking plan management and continuous schema linting, which catches tracking errors in staging before invalid payloads reach production reports.
As discussed on the e-CENS Digital Disruption podcast series, analytics success rests on disciplined foundational governance. Our session on foundational data architecture [Spotify | Apple] examined how data validation prevents the reporting discrepancies that destroy stakeholder trust. Our episode on global privacy compliance [Spotify | Apple] detailed how privacy-by-design protects organizations against regulatory exposure.
What Is the Implementation Roadmap for a Dual-Stack Analytics Foundation?
The roadmap runs in four structured phases:
- Phase 1: Discovery and Business Alignment (Weeks 1 to 3): Interview marketing, product, and engineering stakeholders. Define conversion metrics, audit existing tags, and set regulatory boundaries that determine platform requirements.
- Phase 2: Universal Tracking Plan Design (Weeks 4 to 6): Construct a vendor-neutral event tracking dictionary. Standardize event names, property objects, user identity keys, and schema validation rules across every digital touchpoint.
- Phase 3: Server-Side Pipeline Deployment (Weeks 7 to 10): Implement server-side Google Tag Manager or a customer data router. Configure single-dispatch telemetry, identity mapping, and simultaneous streaming endpoints to GA4 and Amplitude.
- Phase 4: Enablement, Warehouse Sync, and Activation (Weeks 11 to 14): Connect both engines to the enterprise lakehouse. Set up automated cohort synchronization from Amplitude into advertising networks, and onboard marketing on GA4 and product squads on Amplitude.
The analytics foundation decides whether an organization moves with agility or struggles with fragmented data silos. e-CENS is a certified partner for both Google Marketing Platform and Amplitude, and we provide unbiased technical architecture, enterprise implementation, and data activation services. Contact our enterprise analytics architects to design your scalable data foundation.
Frequently Asked Questions
What is the primary difference between Amplitude and Google Analytics 4?
Google Analytics 4 is a top-of-funnel marketing attribution platform: media acquisition tracking, web campaign ROI, and Google ad ecosystem integration. Amplitude is a post-acquisition product analytics platform: in-app user flows, retention cohorts, and feature engagement. GA4 measures how users discover a digital presence, and Amplitude explains how they extract value from a product.
Can an enterprise run both Amplitude and Google Analytics 4 concurrently without tracking discrepancies?
Yes. Data parity comes from one unified server-side ingestion layer or customer data platform. Standard event naming taxonomies and user identity keys at collection give both tools identical raw inputs, while each tool serves its own operational objective across marketing and product teams.
How do GA4 and Amplitude differ in event data limits and schemas?
Standard GA4 is a flat key-value model capped at 25 custom parameters per event, so deep multi-property modeling needs BigQuery exports. Amplitude is a nested JSON model with no flat property cap, which enables behavioral cohorting and exploratory funnel analysis without SQL overhead.
How does user identity resolution compare between the two platforms?
Amplitude links anonymous device identifiers to internal User IDs through server-side aliasing, so pre-login and post-login sessions unify retroactively. GA4 uses a four-tier reporting identity of User-ID, Google Signals, Device ID, and modeled data, which brings data thresholding and reporting delays when privacy thresholds trigger.
Which platform offers superior compliance for regulated industries like healthcare and finance?
Amplitude is a dedicated first-party data processor with European Union cloud hosting and Business Associate Agreements for HIPAA compliance. Google Analytics 4 is a Google advertising infrastructure product that does not execute HIPAA BAAs and faces European scrutiny over international data transfers.
Planning the move to GA4? e-CENS runs enterprise GA4 migration programmes: audit, tracking design and a 12-week cutover.
Mostafa Daoud

