Database Migration

Database Migration

Database Migration moves Sybase ASE schemas (and optionally data) to SQL Server or Azure SQL through a guided pipeline: assess → convert → deploy → verify.

Open Migration in the sidebar (/migration), or start from home Migrate Database. For a short first-run checklist, see Database Migration quick start.

Not application modernization — Migration user stories & tracking covers build / migrate / decommission work in ALM. This page is the database pipeline only.

Why use it?

The value: a repeatable Sybase → SQL Server path with live progress, remediation hooks, and an auditable completion report — not a pile of one-off scripts.

Pick a strategy

Choose how you provide the source when you create the migration:

Both strategies need a SQL Server target connector for deploy. Only SSMA Direct also needs a Sybase ASE source connector.

Supported pairs today: Sybase ASE → SQL Server and Sybase ASE → Azure SQL. More targets are coming. Snowflake is not a Database Migration endpoint (use it only for journey Pull Sources).

Before you start

1. Add connectors

Create and Test them under Connectors. Wizard empty state: No Sybase connectors configured. Add one from the Connectors page.

2. Choose a target database name

Provide a target database name (often defaults to the source DB name). Validation warns if that database already exists — it may be overwritten.

3. Confirm network reachability

Workers must reach Sybase (5000) and SQL Server (1433). If SSMA stays unavailable or connections fail after correct credentials, ask your platform admin to check Migration worker config.

How to start a migration

Option A — From home

1. Open / → click Migrate Database (Assess → Convert → Deploy → Verify).
2. Fill the inline wizard:
   • Migration Name
   • Source Platform / Target Platform (optional versions)
   • How will you provide the source? (Sybase Connector or file/SQL modes)
   • Target Connector (SQL Server) + Target Database Name
3. Click Start Migration → opens /migration/:id.

Option B — From the Migration hub

1. Sidebar Migration → + New Migration (/migration/new).
2. Complete three steps:
   1. Project Info — name and description
   2. Source & Target — platforms, source mode, connectors or files, target DB
   3. Review — confirms Conversion Strategy (SSMA vs AI-assisted)
3. Click Start Migration.

After create, Forge may auto-ingest the source (live browse or uploaded SQL) in the background.

Portfolio (/migration)

Use the hub to find and resume work:

Empty: No migration projects yet. → + New Migration.

Database projects also appear under My Projects with a migrate type filter.

Journey: six stages

Each project at /migration/:id uses this sidebar pipeline. Work left to right.

Overview → Validate → Discover → Deploy & Migrate → Report → Complete

1. Overview — review & configure

Purpose: Confirm name, source → target, strategy badge, connectors, and status before you spend a run.

Do this:

1. Check Source and Target cards (edit with the pencil if needed).
2. Use Configure (gear) only if you need a full reconfigure.
3. Click Proceed to Validate.

Mid-run you may see View Live Execution. After success: KPIs and View Detailed Report.

2. Validate — verify connectivity

Purpose: Pre-flight before discovery so bad credentials or missing target DB fail early.

Do this:

1. Wait for the checklist (Pass / Warn / Fail).
2. On failure → fix settings in Overview → Re-run checks.
3. When checks pass or only warn → Proceed to Discover.

3. Discover — analyze source schema

Purpose: Inventory databases, objects, and tables; for SSMA, see Migration Compatibility.

Do this:

1. Click Start Discovery if the schema is not scanned yet (Scanning Source Schema…).
2. Review Databases / Total Objects / Tables and the object list.
3. On SSMA: review Migration Compatibility (predicted success %, compatible objects, known issues, SSMA Available / SSMA Unavailable).
4. Click Proceed to Deploy & Migrate.

Use Refresh if counts look stale. Re-discover from the header resets discovery when you need a clean scan.

4. Deploy & Migrate — execute

Purpose: Convert and deploy (and optionally migrate data) with a live execution console.

Do this:

1. Choose Migration Scope:
   • Full Migration — schema + data
   • Schema Only — schema first (safer first pass)
2. Review Deployment Summary (engine, DBs, credentials).
   • SSMA: SSMA (K8s Pod)
   • File/AI: Opsera Conversion Engine
3. Click Start Migration.
4. Watch the bottom execution console:
   • Timeline — phase progress
   • Console — live logs
   • Errors — failures and remediation

Typical SSMA phases: load engine → prepare scripts → connect → convert schema → deploy → data migration → verification → complete.

If objects fail: use AI Remediation, Retry SSMA (SSMA path), or Skip. Header Cancel stops an in-flight run; Retry Migration after a failed deploy.

5. Report — view results

Purpose: Prove what landed and download artifacts.

Look for:

• Object success rate and type breakdown
• Data Comparison — Source vs Target / row integrity
• Migration Artifacts (SQL bundle, developer package, validation / SSMA / assessment reports when present)
• Execution History (paginated) with per-run report and logs

Empty: No detailed report data available for this run / No executions yet.

6. Complete — final summary

Purpose: Close the loop with a clear outcome.

You’ll see Migration Complete or Migration Completed with Warnings, plus source/target, strategy, object counts, and executions → View Detailed Report.

From the header after complete you can start a New Migration on the same project when you need another run.

Status meanings (common)

Troubleshooting

Tips

• Prefer Schema Only on the first pass, then Full Migration once the schema looks right.
• Confirm Conversion Strategy on the Review step before you click Start Migration.
• Keep connectors tested — most Validate failures are credentials or unreachable hosts.
• Download the SQL Bundle and Migration Report from Report for handoff and audit.
• Use portfolio Awaiting Approval to find runs waiting on a human gate after discover/assess/convert.

Related

• Database Migration quick start — short first-run checklist
• Connectors — Sybase ASE & SQL Server
• Migration user stories & tracking — application modernization ALM (different product)
• Pull Sources — Sybase/Snowflake as journey context (not this pipeline)