Snowflake migration services
Snowflake migration services, and how to choose between migration companies
For data leaders moving a warehouse from Teradata, Oracle, SQL Server, Redshift, Netezza or Hadoop to Snowflake. NTech, a Snowflake Partner Network member, delivers an inventory and wave plan, target architecture, code conversion with Snowflake's SnowConvert AI plus engineer review, history and incremental loads, table- and report-level reconciliation, a parallel run until each wave is signed off, and a cost review after go-live. A principal architect in the US or Europe owns the design; engineers in India overlap 09:00–13:30 US Eastern.
Quick answer
How do you choose a Snowflake migration services company?
Choose by the shape of your estate, not the size of the firm. Large systems integrators suit multi-country programs that need a migration factory across many systems. Specialist Snowflake partners suit one to a few source platforms with senior engineers doing the work. Staff augmentation suits teams that own the plan. Ask every candidate for a sample reconciliation report and a wave plan, and check partner status in Snowflake's partner directory.
Decision guide
How to choose a Snowflake migration company
Snowflake runs partner programs for services firms, including designations for migration-focused partners, and has its own professional services team. Buyers can check any firm's partner status in Snowflake's partner directory on snowflake.com. Status tells you a firm is recognized by Snowflake; the comparison below is about fit.
| Large systems integrators | Specialist Snowflake partners | Staff augmentation | |
|---|---|---|---|
| Best fit | Multi-country programs with many source systems, application changes and formal procurement | One to a few source platforms; data teams that want senior engineers hands-on | Teams that already own the plan and architecture and need capacity |
| How they work | Migration factory: standard templates, accelerators and large delivery centers running many waves in parallel | Small pods led by an architect; the same people assess, convert and reconcile | Engineers join your team and work your backlog |
| Strengths | Scale, breadth beyond data (applications, change management), global coverage | Depth in Snowflake and the source dialect, quick start, direct access to the people doing the work | Flexible capacity, you control priorities, simple monthly pricing |
| Trade-offs | Longer mobilization and more management layers; ask who will actually do the work | Less capacity for very large parallel programs; narrower scope outside data | You carry delivery risk, design and sign-off |
| Usual pricing | Program or milestone based | Fixed scope by milestone, or a dedicated team per month | Per person, per month |
Questions to ask every candidate
- Is the estimate based on query logs and usage, or a raw object count?
- Which conversion tools will you use, and what do engineers do after them?
- Which reconciliation levels do you run, and who signs off each wave?
- How long is the parallel run, and how will you control credits during it?
- Who is the named architect, and how many hours overlap with our team?
Evidence to request
- An anonymized object inventory and reconciliation report
- A wave plan with cutover and fallback criteria
- Their partner status, checked in Snowflake's directory
- Security controls for access, masking and offboarding
- A handover plan so your team can run the platform
NTech works as a specialist partner on fixed-scope projects, dedicated teams or staff augmentation. If you only need engineers, see hire Snowflake developers.
By source
Snowflake migration by source platform: key issues and tools
Snowflake's SnowConvert AI converts SQL from all six sources below. In June 2026 Snowflake announced Snowflake AIM, a migration platform built on SnowConvert AI, the Snowpark Migration Accelerator and Datometry. We confirm current tool coverage at kickoff.
| Source | Key issues | Tools we typically use |
|---|---|---|
| Teradata | BTEQ, FastLoad, MultiLoad and TPT scripts; SET tables that silently drop duplicates; primary indexes; macros; case-insensitive columns | SnowConvert AI, Teradata Parallel Transporter exports, COPY INTO, Datometry where a lift-and-shift first makes sense |
| Oracle (cloud options) | PL/SQL packages, sequences, CONNECT BY queries, materialized views, implicit date and NULL behavior | SnowConvert AI, Oracle Data Pump or SQL extracts, CDC with tools such as Fivetran or AWS DMS |
| SQL Server / Azure Synapse | T-SQL procedures, SSIS packages, #temp-table patterns, identity columns, collation differences | SnowConvert AI (including SSIS to dbt projects), Azure Data Factory, CDC tools |
| Amazon Redshift | SQL is close; distribution and sort keys removed, UNLOAD/COPY jobs moved, Spectrum tables, concurrency settings rechecked | SnowConvert AI, UNLOAD to S3 then COPY INTO, external tables or Iceberg tables |
| Netezza | nzsql scripts, distribution keys, zone-map assumptions, often prompted by older appliance hardware reaching end of support | SnowConvert AI (PostgreSQL/Greenplum/Netezza dialect), external table exports, COPY INTO |
| Hadoop / Hive / Spark | HiveQL, partitioned file layouts, small-file problems, Spark jobs | SnowConvert AI for HiveQL and Spark SQL, Snowpark Migration Accelerator for PySpark and Scala, Iceberg tables |
Method
A migration factory method, sized for one data team
Large firms call it a migration factory: every wave goes through the same stations, with the same templates, checks and sign-off. We use the same idea with a smaller, senior team, so the second wave is faster than the first and nothing reaches production unreconciled.
Assess
Inventory tables, views, procedures, jobs and downstream reports from query history and usage logs. Mark each object to move, rewrite or retire, and run SnowConvert AI's assessment for a conversion estimate.
Design
Target architecture: databases and schemas, warehouse sizing, role model, masking policies, ingestion pattern, and a wave plan grouped by business domain. See Snowflake implementation.
Build the factory
Repository, CI checks, conversion settings, naming standards, reconciliation scripts and a sign-off template, set up once and reused for every wave.
Convert
Automated conversion first, then engineers fix and test what automation flags: procedures, dialect edge cases, scheduling. A senior engineer reviews every pull request.
Move data
Historical load through stages and COPY INTO, then incremental or CDC feeds so Snowflake stays current during the parallel run.
Validate in parallel
Run old and new side by side. Compare schemas, row counts, aggregates, row hashes and key reports until business owners sign off.
Cut over and retire
Switch consumers wave by wave, keep a short read-only fallback, monitor cost and performance, then decommission legacy jobs.
Reconciliation and parallel run
How each wave proves the numbers match
| Check | What is compared | Catches |
|---|---|---|
| Schema | Columns, data types, precision, nullability | Truncated decimals, wrong timestamp types |
| Row counts | Per table and per load date or partition | Missing files, rejected rows, duplicates |
| Aggregates | SUM, MIN, MAX, COUNT DISTINCT, null counts | Rounding, NULL handling, date conversion |
| Row hashes | Hash per row or key range on both platforms | Single changed values that aggregates hide |
| Reports | Key dashboards and extracts with the same parameters | Logic differences: case sensitivity, date arithmetic |
| Sign-off | Business owner approval per domain | Anything the tests did not anticipate |
- Parallel-run length: at least one full business cycle per wave, including a month-end close where finance reports depend on it.
- Same data cut: both platforms load the same source data, so differences point to logic, not timing.
- Every difference closed: fixed, or explained and accepted in writing.
- Credits watched: resource monitors and auto-suspend keep the double-running period within budget.
What you get
Deliverables
- Migration inventory, retire list and wave plan
- Target architecture, role model and warehouse plan
- Converted, tested code in your repository
- Rebuilt pipelines and orchestration (dbt, Airflow or Snowflake Tasks)
- Reconciliation reports for every migrated table and key report
- Runbooks and a handover to your team or ours
- A cost review once workloads are live
Case study: parallel run in a regulated migration. For a financial services client, our team moved a mainframe core-banking system (not a data warehouse) to a cloud-native architecture over 18 months with 12 senior engineers. The migration was phased with a parallel run, completed with zero downtime, and passed a regulatory audit with no findings. The same parallel-run discipline applies to warehouse migrations. Read the case studies.
Cost and time
What drives the cost and length of a Snowflake migration
Data volume is rarely the main driver. Code, consumers and proof are.
| Driver | Why it matters | How to reduce it |
|---|---|---|
| Procedural code | Procedures, BTEQ, PL/SQL and SSIS need engineer time after conversion | Retire unused code; replace transformation logic with dbt models |
| Reports and extracts | Each consumer must be repointed and reconciled | Use query logs to retire unused reports before the wave plan |
| Parallel-run length | Two platforms run, and are paid for, at once | Short waves, clear sign-off criteria, right-sized warehouses |
| Data quality in the source | Existing errors surface as reconciliation differences | Agree tolerances and known issues up front |
| Re-architecture scope | Redesigning models while migrating adds work and risk | Migrate like for like first; improve after cutover |
| Decision speed | Waves stall waiting for sign-off | Name a sign-off owner per domain at the start |
We give a timeline and estimate after the assessment, broken into waves. The risks below are the ones that most often add time late in a project.
| Risk | What it looks like | How we handle it |
|---|---|---|
| Silent result differences | Reports differ because of case sensitivity, NULL handling, rounding or date logic | Table and report reconciliation in every wave, signed off by business owners |
| Hidden dependencies | An extract or spreadsheet nobody listed breaks after cutover | Usage logs and query history mapped before the wave plan is fixed |
| Procedural code | Stored procedures and scripts take longer than the SQL | Automated conversion first, then senior review of every procedure |
| Cost surprises | Credit spend jumps during the parallel run | Right-sized warehouses, auto-suspend and resource monitors from day one |
| Big-bang cutover | Everything switches at once and rollback is impossible | Wave-by-wave cutover with the legacy system kept until sign-off |
Tools we use, chosen per source:
- SnowConvert AI
- dbt
- Snowpipe
- COPY INTO and stages
- Fivetran
- Airbyte
- AWS DMS
- Azure Data Factory
- Airflow
- Teradata Parallel Transporter
- Great Expectations
- Custom reconciliation scripts
Contact us
Plan your Snowflake migration
Tell us what you're moving from and roughly how big it is. A senior data architect will reply with next steps.
- A senior engineer reads every message
- Reply within one business day
- No obligation, and your details are used only to reply
Prefer the full form? Go to the contact page.
FAQ
Questions buyers ask us
How do you choose a Snowflake migration services company?
Match the firm to your estate. Large systems integrators suit multi-country programs with many systems; specialist Snowflake partners suit one to a few source platforms with senior engineers hands-on; staff augmentation suits teams that own the plan. Ask for a sample reconciliation report and wave plan, and check partner status in Snowflake's partner directory.
What is a migration factory?
A repeatable process where every migration wave passes through the same stations (assess, convert, load, validate, cut over) with standard templates, automated checks and a sign-off step. Large firms run it with big delivery centers; the same method works with a small senior team.
Should we use a large systems integrator or a specialist Snowflake partner?
Use a large systems integrator when the migration is one part of a wider program across many countries, applications and source systems. Use a specialist partner when the scope is one to a few data platforms and you want the architect and engineers who plan the work to do it. Some companies combine both.
How do we check a company's Snowflake partner status?
Snowflake lists its services partners and their program designations in the partner directory on snowflake.com. Check the firm there rather than relying on logos on its website. NTech is a member of the Snowflake Partner Network.
How long does a Snowflake migration take?
It depends on the number of objects, the amount of procedural code and how many reports and systems depend on the warehouse. We give a timeline after the assessment, broken into waves so the first domain goes live early.
How much does a Snowflake migration cost?
Cost is driven mostly by the amount of procedural code, the number of pipelines and reports to reconcile, and the length of the parallel run, not by data volume. An assessment gives an object-by-object estimate before you commit.
Which tools are used to migrate to Snowflake?
Common tools are Snowflake's SnowConvert AI (now part of Snowflake AIM) for code conversion, stages with COPY INTO or Snowpipe for loading, replication tools such as Fivetran or AWS DMS for change data capture, dbt for rebuilt transformations, and reconciliation scripts or Great Expectations for validation.
Can we keep the old warehouse running during migration?
Yes. We recommend a parallel run for each wave until reconciliation passes and business owners sign off, then a short read-only fallback before the legacy jobs are retired.
Can stored procedures be migrated to Snowflake?
Yes. Procedures from Teradata, Oracle and SQL Server are converted to Snowflake Scripting, JavaScript or Python procedures, or replaced with dbt models where the logic is really a transformation.
Next step
Tell us what you need to build or who you need to hire.
A 30-minute call with a senior architect. You leave with a scoped plan or a role profile, whether or not you work with us.