Migration Guide: How to Move QuickBooks Database Manager to a New Server

Migrating QuickBooks Database Server Manager (QBDBSM) to a new server involves moving your company files, installing the database server components on the new operating system, updating network shares, and redirecting workstations to the new location. A successful migration requires maintaining proper NTFS folder permissions, configuring firewall rules, and scanning directories to establish multi-user hosting without interrupting daily accounting workflows.

Fast-Fix: Migrate QBDBSM to a New Server

To migrate QBDBSM to a new server, back up your company file and copy it to the new server. Install QuickBooks Database Server Manager using the Custom and Network Options installer. Share the data folder with Full Control permissions, configure Windows Firewall inbound rules for QuickBooks database ports, and run a folder scan in QBDBSM. Finally, remap the network drive on each workstation to point to the new server.


Quick Status & Triage Snapshot

  • Data Risk Tier: Moderate (moving company files requires creating verified backups prior to transfer to prevent data loss).
  • Multi-User Impact: High (all accounting users must pause work during the server cutover).
  • Common Trigger: Server hardware upgrades, operating system retirements, or transitioning from peer-to-peer hosting to a dedicated server.
  • Estimated Migration Time: 1 to 2 hours.

Pre-Migration Checklist

Complete these tasks before making system changes:

  1. Schedule Downtime: Ensure all accounting staff exit QuickBooks Desktop.
  2. Create a Full Backup: Inside QuickBooks, go to File > Back Up Company > Create Local Backup. Save the backup file (.qbb) to an external drive or secure cloud storage.
  3. Record Version and Release Details: Press F2 on an active workstation to identify your exact year and maintenance release (e.g., QuickBooks 2026 R3).
  4. Prepare the New Server: Assign a static IP address to the new server to avoid connection drops from changing DHCP leases.

If your new machine is running modern server software, review Windows Server 2025: Setting Up QuickBooks on a Dedicated Server before beginning.


Step-by-Step Server Migration Procedure

Phase 1: Backup & Old Server Decommission
Phase 2: Install QBDBSM on New Server
Phase 3: Folder Sharing & Security Configuration
Phase 4: Windows Firewall Rule Deployment
Phase 5: Database Scan & Workstation Remapping

Step 1: Decommission Hosting on the Old Server

To prevent network conflicts, stop the database services on the old machine before bringing the new server online:

  1. Log in to the old server.
  2. Press Windows Key + R, type services.msc, and press Enter.
  3. Locate QuickBooksDBXX and QBCFMonitorService.
  4. Right-click each service, select Properties, change the Startup type to Disabled, and click Stop.
  5. Disconnect the old network share or rename the shared folder to prevent accidental access.

Step 2: Install QBDBSM on the New Server

  1. Download the QuickBooks installation setup file that matches the version currently used on your workstations.
  2. Run the installer on the new server.
  3. When prompted, select Custom and Network Options.
  4. Choose: I will NOT be using QuickBooks Desktop on this computer. I will be storing our company file on this computer so other network users can access it.
  5. Complete the installation wizard.

For complete installation steps, refer to the QBDBSM Guide: How to Install and Configure Database Server Manager.

Step 3: Copy Data Files and Configure Folder Permissions

  1. Create a dedicated directory on the new server’s secondary storage volume (e.g., D:\QuickBooksData).
  2. Copy your company file (.qbw) and transaction log file (.tlg) from the backup into this directory. Do not copy old .ND files; let the new server create fresh ones.
  3. Configure Windows permissions:
    • Right-click the folder, go to Properties > Sharing > Advanced Sharing.
    • Share the folder and grant Full Control to network users.
    • Switch to the Security tab and grant Full Control to SYSTEM, Administrators, and the newly created QBDataServiceUserXX.

For complete permission guidelines, see Data Access: Using QBDBSM to Manage Folder Permissions and Access.

Step 4: Configure Windows Firewall Ports

Allow inbound database traffic through the new server’s firewall:

  1. Press Windows Key + R, type wf.msc, and press Enter.
  2. Click Inbound Rules > New Rule.
  3. Select Port > TCP.
  4. Enter the required port numbers for your QuickBooks year:
    • QuickBooks 2026: Port 8019, 55393–55397
    • QuickBooks 2025: Port 8019, 55388–55392
    • QuickBooks 2024: Port 8019, 55383–55387
  5. Allow the connection across all network profiles, name the rule QuickBooks Server Ports, and click Finish.

For specific port details, review Firewall Ports: Configuring Windows Firewall for QuickBooks 2024–2026.

Step 5: Scan Folders in QBDBSM

  1. Launch QuickBooks Database Server Manager on the new server.
  2. Go to the Scan Folders tab.
  3. Click Add Folder, select your new company directory, and click Start Scan.
  4. Ensure the scan finishes with a status of Complete. This step generates new .ND files containing the new server’s IP and port assignments.

Redirecting Client Workstations

Once the new server is hosting the database, update your client workstations:

  1. Open File Explorer on each workstation.
  2. Disconnect the old mapped network drive pointing to the decommissioned server.
  3. Map the new network share using the identical drive letter previously assigned (e.g., Z:). Step-by-step instructions are available in File Access: How to Map a Network Drive for QuickBooks Company Files.
  4. Launch QuickBooks Desktop, open the company file via the new mapped drive path, and confirm that multi-user mode is active.

Closing the Books

Migrating QuickBooks Database Server Manager to a new host modernizes your infrastructure and helps prevent multi-user bottlenecks. By systematically disabling services on the old server, configuring permissions and firewall rules on the new machine, rescanning the data directory, and remapping workstation drives, you ensure a clean, reliable server transition without risking company records.