Start here
Tell us the instance. We reply with a path — or a no.
Work email, what you run today, what you need, and the target (SQL Server 2022/2025, Azure SQL, AWS, Google, Snowflake, Databricks, or another engine you named).
You send: name, work email, company, current system, need, target, timeline.
You get: a human reply with which path fits, what we would need next, or a clear not-a-fit.
You do not get: a price list, a deck, or a newsletter. Nothing is a contract until a written SOW.
Please complete name, work email, company, and the required dropdowns.
Questions
Common questions
What does an assessment cost?
The assessment request is how we start. Delivery is scoped in a written SOW — replica, mapping, and go-live as you need them. We do not publish a price list.
Do you run production go-live, or only hand over a runbook?
Either. We can execute production cutover from the path we proved in the replica, or your team can run the same tested runbook. The SOW says which.
What is AI-assisted here?
Software drafts the inventory, source-to-target map, lineage graph, and recon tests. A named person signs the map before anything moves. We do not skip your UAT, and software does not press go-live unattended.
How do you know the data will match?
In-scope columns get a source-to-target map. We graph how values flow and flag fields that can be produced more than one way. Tests are tied to that map. For banks, those artifacts support BCBS 239 evidence; we do not certify your programme.
Which platforms do you land on?
The one you chose: a supported SQL Server release, Azure SQL, Amazon RDS or Redshift, Google Cloud SQL or BigQuery, Snowflake, or Databricks — including the pipeline pattern that platform expects.
Can you migrate a workload onto SQL Server, not only off it?
Yes. PostgreSQL, MySQL, another SQL Server, Azure SQL, or RDS for SQL Server onto a SQL Server you named — isolated replica, signed map, then we can run go-live. Oracle is in scope when we can prove it in scoping.
Do I have to move to the cloud?
No. A supported SQL Server release on-prem or on an Azure, AWS, or Google VM is a valid target. If you already chose Azure SQL, Amazon RDS, or another engine, we implement that choice.
How long does this take?
Calendar time depends on instance count, Agent jobs, SSIS, and HA. The assessment reply says what we would need next. We do not publish a one-size duration.