Is "migration" the right word for this?
Yes — it's the term most used in the industry when moving from one analytics platform to another, and it's what clients typically call it. Some teams use "re-platforming" or "modernisation," but the work is the same: getting your data and reporting off MCI and onto a new stack with no loss of historical fidelity.
Do we have to decide where we're moving before we start?
No. The discovery phase is specifically designed to help you figure that out. We assess your needs first, then recommend a destination. See Alternatives to MCI for the menu of options we evaluate against.
Can we stay on some MCI components and migrate others?
In some cases yes, but we assess this during discovery. Often a clean migration is more cost-effective than a hybrid setup — keeping MCI alive for a subset of work means you keep paying its row-based fees and supporting two stacks. The deep-dive technical discovery makes the call clear.
What if we have 200 million rows of data?
This is exactly the scenario where a bespoke modular stack (Snowflake / Fivetran / dbt / Tableau or Power BI) typically makes more sense than a like-for-like tool. Row-based pricing breaks down at this scale. We scope the right architecture for high-volume setups during the deep-dive discovery — and we have Snowflake partnership credentials for the warehouse layer.
Will we lose historical data in the migration?
No, preserving historical data is a core part of how we approach every migration. We plan for this explicitly in the deep-dive discovery phase — historical extraction strategy, transformation parity, and validation against MCI's existing reports before cutover.
How long does a migration take?
It depends on the complexity of your current setup and your destination. A straightforward migration can be completed in 8–12 weeks. More complex, multi-source setups typically take 16–24 weeks. The deep-dive discovery gives you a calendar-week plan before you commit to the build phase.
What's the difference between this and the MCI-to-Tableau migration page?
MCI to Tableau Migration is the destination-specific service for teams who've already decided on Tableau. This page is for teams who haven't decided yet, or know they want a different destination — Power BI, Looker Studio, a bespoke Snowflake-based stack, NinjaCat, Adverity, or something else. The discovery phase here is what helps you pick the right destination.
Why Decision Foundry for MCI migration?
Two reasons: (1) 13+ years on MCI / Datorama means we scope migrations accurately and don't over-promise. (2) Cross-platform expertise across every destination tool — Tableau, Power BI, Looker Studio, NinjaCat, Adverity, Supermetrics, Snowflake, BigQuery — so the recommendation isn't biased toward what we know better. We're vendor-neutral on tool selection.