Data migrations on easy mode
Data migrations are a pain in the a**. Not anymore.
GenArk maps the systems you have, designs where your data is going, prices the move, writes the infrastructure code and checks the data before anyone switches over. A senior engineer signs off at every step.
[TODO: Replace with product screenshots]
Why migrations go wrong
Common moves
Examples of migrations GenArk plans
How it works
- 1
Map what you have.
GenArk reads audit logs and system metadata to show how data actually flows between your platforms, including the ones nobody documented.
- 2
Design the target.
It produces a logical architecture, then a physical one once you add detail. Each service shows its features and its compliance coverage, such as HIPAA, GDPR and FedRAMP.
- 3
Price it.
You see the run cost (pay as you go, 1-year or 3-year commitments) and the delivery cost (onshore, offshore or blended teams) before you commit.
- 4
Generate the build.
GenArk writes the infrastructure code (Terraform or CloudFormation), the data models and the DDL scripts, and pushes them to your GitHub.
- 5
Validate and cut over.
A data validator compares source and target, including row counts, file counts and sizes. The old system moves to read-only for a two-week hypercare period so anyone can check a number. Your team decides when to switch traffic over; GenArk never shuts a system down on its own.
- 6
Score and share.
Every plan gets a 1 to 100 readiness score with the gaps to close. Teams can comment, every change is logged, and the whole plan exports to PDF or PowerPoint.
Three levels of detail
Sample plan
Scenario
A finance reporting and contribution margin model moving from Google BigQuery to Databricks on AWS. 50 GB, 50 tables, 10 pipelines.
Architecture
Deliverables
- Architecture diagram
- Run cost and delivery cost scenarios
- Terraform code
- Data model and DDL
- Cutover and validation plan
- Readiness score with recommendations
Readiness score
Gaps to close:
- Example gap: define dev, test and prod environments
- Example gap: confirm data retention policy for source system
- Example gap: identify pipeline owners for sign-off
Migration snapshot
See what your GenArk plan would include. This does not produce an estimate.
Your GenArk plan would include:
- Current-state architecture diagram
- Target-state architecture diagram
- Run cost scenarios (pay as you go, 1-year, 3-year)
- Delivery cost scenarios (onshore, offshore, blended)
- Terraform or CloudFormation code
- Data model and DDL scripts
- Cutover and validation plan
- Readiness score with recommendations
Built for the people doing the work
Control and security
- A person approves every step.
- Every agent action is logged and can be replayed.
- Tenant isolation and PII and PHI controls.
- You can choose which models and regions are used.
- Nothing goes live without your team.
How engagements start
Migration assessment
A fixed-scope engagement that maps your current data flows and delivers a target design, cost scenarios and a readiness score.
Migration delivery
GenArk engineers run the migration with you, or your consulting partner runs it with GenArk.
Consulting firms can use GenArk on their own client work. Partner with us
Frequently asked questions
Does this replace our systems integrator?
No. GenArk accelerates the work your SI or internal team does. It handles the mapping, design, code generation and validation so your team can focus on the decisions and the hard parts.
Can our consulting partner use GenArk?
Yes. Consulting firms can use GenArk on their own client migrations. We work with partners from boutique data consultancies to global SIs.
What if our current systems aren't documented?
That's common. GenArk reads audit logs and system metadata to discover how data actually flows, including the undocumented parts.
How accurate is the generated code?
The generated infrastructure code is a starting point that engineers review and refine. It covers the standard patterns; your team adds the environment-specific details.
Who decides when we switch over?
Your team. GenArk never shuts a system down on its own. The cutover happens when your team is ready, after a hypercare period where both systems run in parallel.
What access does GenArk need to our data?
GenArk reads metadata and audit logs to map your systems. It does not need access to the data itself for the assessment. For migrations, access is scoped to what's needed for validation.
Get a migration assessment
Tell us about your migration and we'll scope an assessment.