Evidence before migration

Know your estate.
Plan your migration.

Bring database inventory, technical findings, and business context into one self-hosted assessment workspace, locally or on Azure.

Read-only metadata collection. Connected or offline.

Database inventory

Northwind / Production
Databases28
Assessed19
Engines4
DatabaseEngineAssessment
orders-prodPostgreSQLCollected
finance-coreOraclePending
customer-360SQL ServerQueued
Illustrative workspace · Sample data, not a live assessment
One estate. A clearer next step.

From inventory to informed decisions.

Connect what your databases tell you with what your stakeholders know. Keep the evidence behind every assessment within reach.

Discover your estate

Organize databases by project, environment, and criticality. Map communication edges and portfolio groups to understand the bigger picture.

Database inventory / Dependencies / Portfolios

Collect the evidence

Run connected discovery agents or upload offline collector results. Add questionnaires and documents for ownership, downtime, and business constraints.

Connected agents / Offline JSON / Stakeholder context

Review the assessment

Bring findings and supporting context into evidence-grounded reports. Review generated recommendations with source snapshots and lifecycle state.

Evidence snapshots / Reports / Practitioner review
Context, not just collection

A recommendation needs a reason.

Technical telemetry is only part of the story. Bring findings, questionnaire answers, documents, dependencies, and portfolios together as bounded report inputs.

Persisted, content-hashed evidence snapshots let practitioners trace the context behind a report and review its recommendations.

Explore the documentation
Assessment contextPractitioner review
Technical findings
Database metadata and engine-specific collection results
Business constraints
Ownership, permitted downtime, and compliance context
Supporting evidence
Documents, questionnaire answers, and source snapshots
Report lifecycle
Generated recommendations for review and approval
Illustrative evidence summary · Not a generated report
Engine coverage

Seven plugin families.
Readiness made explicit.

One collection workflow, with validation status visible for each implemented engine plugin.

PostgreSQLRepository E2E tested
OracleLive certification needed
SQL ServerLive certification needed
MySQLLive certification needed
MongoDBLive certification needed
CassandraLive certification needed
SAP / Sybase ASELive certification needed

Assessment support is not production certification. PostgreSQL has repository end-to-end coverage. Other implemented plugins need representative live-version certification. Validate versions, permissions, and generated recommendations before production use.

Designed for network boundaries

Collection stays close to the source.

The portal never connects directly to source databases. Agents execute engine plugins locally and initiate outbound HTTPS calls to return structured findings.

  • Local database credentials and read-only metadata collection; application rows are not queried.
  • Per-agent pre-shared keys and HMAC-SHA256 request signatures.
  • Offline collectors and validated JSON uploads when a persistent agent is not appropriate.
Customer network
Source databasesMetadata collected locally
Discovery AgentEngine plugins + local credentials
Agent ↓ Outbound HTTPSAlternative: offline collector → JSON export → upload
Assessment platform
Portal APISigned agent requests / Offline uploads
WorkspaceInventory, evidence, and reports
Collection paths from customer network to assessment platform
Deploy to Azure

Your workspace.
Your Azure subscription.

Run the toolkit on Azure Container Apps using the repository's Bicep templates and PowerShell deployment workflow. Host the assessment platform in your subscription while customer-network agents continue to collect locally.

Configure your target environment and secrets, build and start the local application containers, then validate and review the infrastructure preview before deploying.

Azure resource charges apply. Review region availability, sizing, permissions, and the deployment preview for your environment.

Built for your environmentBicep infrastructure
Application hosting
Azure Container Apps for the frontend, API, worker, and platform Discovery Agent
Assessment data
Azure Database for PostgreSQL Flexible Server, with Azure Files for persisted configuration and Data Protection keys
Container images
Azure Container Registry with managed-identity image pulls and timestamped image tags
Review before deployment
Validate → WhatIf → Deploy through the existing PowerShell deployment script
Your infrastructure. Your workspace.

Start locally.
Explore your estate.

Build the artifacts, configure local secrets, and start the portal, API, worker, PostgreSQL, and platform agent with Docker Compose.

Before you start
Git, Docker 24+, .NET 8 SDK, Node.js 24 LTS + npm, and PowerShell 7+.

PowerShell 7+
git clone https://github.com/prjelesi/DBMigrationAssist.git
cd DBMigrationAssist
dotnet restore src/AssessmentToolkit.sln
.\build.ps1
Copy-Item .env.example .env
# Edit .env and configure local secrets before starting.
docker compose build
docker compose up -d

Images use pre-compiled output, so build first. Configure your .env values before starting services; see the setup guide for required settings.