Migrating a QuickBooks Desktop Company File to a New Domain or Workgroup

Relocate an active company file across a domain or workgroup change without stranding users, covering UNC remapping, .ND regeneration, and Database Server Manager re-scan.

When a network domain changes or a workgroup is restructured, QuickBooks Desktop multi-user access typically breaks because the hosting configuration, UNC paths, and folder permissions are all tied to the old network identity. This playbook walks through relocating the company file and restoring full multi-user hosting in a controlled, reversible sequence.

When to Run This Playbook

Run this playbook when the server hosting the company file is being joined to a new domain, when a workgroup is being renamed, or when the file is being moved to a new server entirely. If only user workstations are changing domains but the file server and its name remain unchanged, a lighter permission refresh may suffice. Do not attempt this during open accounting periods; schedule it for a window when no users need access to the file.

Phase 1: Pre-Migration Snapshot and Backup

Before touching anything, create a verified backup of the company file (.QBB) and place a copy of the working file (.QBW), the transaction log (.TLG), and the Network Data file (.ND) in a separate rollback folder on local storage. Note the current UNC path (for example, \\OLDSERVER\QBData\Company.qbw) and the folder's share and NTFS permissions. Document which users had Full Control, Change, and Read access. This snapshot is the rollback point; if anything downstream fails, the file can be restored to its original location and the old server configuration reactivated.

Phase 2: Prepare the Target Server and Folder

On the new server (or the same server under its new domain identity), create a shared folder such as QBData. Set share permissions to allow the appropriate domain group Full Control or Change access. Set NTFS permissions so that every QuickBooks user — and the domain account running the QuickBooksDB service — has Full Control at the folder level. Apply permissions to subfolders and files. Disable Simple File Sharing if it is enabled. Confirm the server's new hostname and that it resolves from at least two workstations via ping.

Phase 3: Stop Hosting and Move the File

On the old server, open QuickBooks Database Server Manager and stop hosting. Close QuickBooks on all workstations. Copy the .QBW file (and the .TLG if the file was not properly closed) to the new shared folder. Do not copy the .ND file from the old location; it will be regenerated fresh in the next phase. Verify the copied file opens in single-user mode on the server itself before proceeding.

Phase 4: Regenerate the .ND File and Re-scan

This is the step that restores multi-user access. On the new server, open QuickBooks Database Server Manager. Under the Scan Folders tab, add the new shared folder path and click Scan. The scan creates a fresh .ND file with the correct server name, domain context, and UNC path. Verify the scan completes without errors and that the company file appears in the results list. If the file does not appear, confirm the folder permissions allow the Database Server Manager service account full read/write access and re-scan.

Phase 5: Reconfigure Workstation Access

On each workstation, open QuickBooks while holding the Ctrl key to bypass the open-file dialog, then close the company file. Use the Open Previous Company list or browse to the new UNC path directly — do not use a mapped drive letter, as QuickBooks relies on UNC paths for reliable hosting. Open the file in multi-user mode. If a workstation cannot find the file, verify that the .ND file in the new folder references the correct server name and that the workstation can reach that UNC path from File Explorer. If a damaged .ND file is suspected, delete it and re-scan from the server.

Phase 6: Verify Clean Outcome

A successful migration looks like this: the file opens in multi-user mode from every workstation, the Hosting mode on each workstation reads "Only this computer" (not "Hosting on"), and the server shows "Hosting on for this computer only." Simultaneous access from two or more workstations confirms the configuration. Check the Product Information screen (press F2) to verify the file path reflects the new UNC location. If users encounter errors such as -6123, 0 or H-series codes, the most common cause is a stale .ND file or insufficient folder permissions; revisit Phase 4 and Phase 2 respectively.