SQL Server Database Migration

Migrate from Microsoft SQL Server databases

Move Your SQL Server Database, Even When the Server Is Gone

Univik reads your SQL Server database straight from the file and exports it to the format your target needs. Move to a new SQL Server, to MySQL or PostgreSQL, to Access or to CSV and Parquet for analytics. The source can be detached, offline, corrupt or a backup file.

Free Download
100% Safe & Secure

Buy Now
Starting from $99

No SQL Server Needed: Read the source file directly, with no live connection.
Schema Intact: Keys, indexes, constraints, views and stored procedures come with the data.
Any Target: A SQL script, CSV, Access or a live SQL Server restore.
Offline and Corrupt Tolerant: Migrate from files that other tools cannot open.

Univik SQL Server migration box

The Univik Role

How Univik Helps You Migrate

The hard part of any migration is getting a complete and accurate copy of the source out. Univik does exactly that, even when the database will not attach.

Reliable Source Extraction

Reads the MDF, NDF or BAK at the page level, so you get every table even from an offline or corrupt database.

Your Schema Comes With It

The SQL script export carries keys, indexes, constraints, views, stored procedures, functions and triggers.

Portable Formats

Export a SQL script or CSV that any database can import, plus an Access file for the desktop. CSV needs no dialect changes.

Direct SQL Server Restore

Push tables straight into a new SQL Server with CREATE TABLE and bulk copy, ready for a version upgrade or a server move.

No Live Connection

The source never has to be running or attached. Migrate from a detached file, a backup or a copy on any Windows PC.

Read Only and Safe

The source is opened read only and never changed. There is no risk of data loss, so the migration is safe to run against production data.

The Most Common Move

Migrate to Another SQL Server

Most migrations stay on SQL Server. Upgrade to a newer release, move to new hardware or rebuild after the old server is gone. Univik reads the source file and hands you a clean copy to load anywhere.

Upgrade to a Newer Version

Moving from an older release to a newer one. Restore the tables directly into the new instance or run a SQL script export.

Downgrade to an Older Version

A native backup cannot restore onto an older SQL Server. A SQL script export runs on any version, so you can move a database down.

When the Server Is Gone

The old server crashed or was retired and only the file survives. Univik reads the detached or offline file and rebuilds the tables on a new server.

Approaches

Three Ways to Migrate a SQL Server Database

Every migration is one of three moves. Univik supports all three from the same source file.

To Another SQL Server

Moving up a version or over to a new server. Export a SQL script or restore the tables directly into the target instance.

To a Different Engine

Moving to MySQL, PostgreSQL or Oracle. Export a SQL script or CSV, then import it into the target. See the migration paths below.

To Files or Analytics

Leaving a database behind for storage or reporting. Export to CSV, Excel or Apache Parquet for a data lake or archive.

Migration Paths

Where You Can Migrate To

Pick your target for a step by step path. Univik always handles the source side.

SQL Server to MySQL

Export a SQL script or CSV from the source, then load it into MySQL or MariaDB.

SQL Server to PostgreSQL

Extract the tables to a portable format, then import them into PostgreSQL.

SQL Server to SQL Server

Upgrade the version or move servers with a SQL script export or a direct restore.

SQL Server to Access

Export the tables straight to an Access database for a small desktop app.

SQL Server to CSV or Parquet

Move the data into files for a warehouse, a data lake or long term archive.

Corrupt Source First

If the source will not open, repair it with SQL Database Recovery, then migrate.

The Steps

How the Migration Works

Four steps from a source file to a working target.

Open the source file: Select the SQL Server MDF, NDF or BAK file. No SQL Server and no attach is needed.
Preview and select tables: Open any table to review the data, then choose the tables to migrate.
Export to your target format: Export a SQL script, CSV or Access file. A live SQL Server restore is also available.
Import into the target: Run the SQL script or import the CSV into the target, from a new SQL Server to MySQL or PostgreSQL.

Plan Ahead

SQL Server Migration Checklist

A short list to keep a migration clean and safe.

Work from a copy: Take a backup or a detached copy of the source, then migrate from that rather than the live file.
Recreate the logins: Server logins and SQL Agent jobs live on the server, not in the database file, so set those up on the target.
Export schema and data: Use Univik to export a SQL script that carries the tables, keys, indexes, views and stored procedures.
Verify row counts: After the import, check that every table holds the same number of rows as the source.
Test before you switch: Point a test copy of the application at the target and confirm it runs before you go live.

Comparison

Univik vs Manual Migration

See how it compares to detach and attach or hand written scripts.

Univik

Works Offline: Reads a detached, offline or corrupt source with nothing running.
Schema Intact: Keys, indexes, constraints and programmable objects come along.
Portable Output: A SQL script or CSV that any target can read.
Whole Database: Reads the primary MDF plus every NDF file in one pass.
Read Only: The source is never touched.

Detach, Attach and Scripts

Server Required: The source must be running and healthy to script it.
Breaks on Corruption: A suspect database blocks the whole move.
Manual Schema: You rebuild every table definition by hand.
File by File: Multi file databases are handled one at a time.
Risk to Source: Detach and attach can leave the source in a bad state.

Data Sheet

Migration Tool Specifications

Product details, source support and requirements.

Product Name:	Univik SQL Server Migration
Version:	6.7 (Latest)
Source Files:	SQL Server MDF (.mdf), NDF (.ndf) and BAK (.bak), detached, offline, corrupt or a backup.
Source Versions:	SQL Server 2000 to 2025
Targets:	A SQL script, CSV, Excel, JSON, XML, Apache Parquet, Access or a live SQL Server restore.
Platforms:	Windows 11 and 10 (64-bit), Windows Server 2016 and later.
Prerequisites:	.NET Framework 4.8 or higher. No SQL Server or SSMS needed.
License Price:	Starting from $99 Buy Now

Help & Support

Migration Questions

Common questions about migrating a SQL Server database.

Yes. Univik reads the source database file directly from disk, with no SQL Server, no ATTACH and no instance. You only need read access to the file and .NET Framework 4.8 or higher on Windows.

Yes. Export a SQL script with schema and data that runs on any version. You can also use the built in restore tool to push tables straight into the target server. This works for version upgrades and for moving a database to a different server.

Univik handles the source side. Export the tables to a SQL script or CSV, then import them into MySQL or PostgreSQL. CSV is read by every database and needs no dialect changes. See the SQL Server to MySQL and SQL Server to PostgreSQL paths for step by step guidance.

Yes. The SQL script export carries the full structure, including primary and foreign keys, indexes, check constraints, views, stored procedures, functions and triggers, so the target is a faithful copy of the source.

Yes. Univik reads the file at the page level, so it can extract data from detached, offline and corrupt databases that will not attach. For heavily damaged files, run Univik SQL Database Recovery first, then export.

Source databases from SQL Server 2000 through 2025 are supported, including 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019 and 2022. The version and collation are read from the file automatically.

No. The source file opens in read only mode and is never modified. All output goes to new files you choose, so the migration is safe to run on production data.

Yes. Preview every table, then select the ones you want to move. You can migrate a single table or the whole database in one run.

Yes. A native backup or detach cannot go to an older version, but a SQL script export runs on any version. Export the schema and data as a script, then run it on the older SQL Server.

Server logins live in the SQL Server master database, not in your database file, so they do not travel with a migration from the file. Plan to recreate the logins on the target server. The tables, data, keys, indexes, views, stored procedures and triggers all come across in the SQL script export.

Still have questions? Contact support or Live Chat

Related Tools

Explore More Univik Tools