Merge Fails With Target Chaining Errors: Repair First

QuickBooks Desktop stops a company-file merge with target chaining errors. This guide gets both files healthy so the merge can finish.

When two QuickBooks Desktop company files are merged, every transaction in one file is re-pointed at matching list entries in the other. Before it writes anything, the merge checks that the internal links in both files are sound. If a link is broken, the process stops with a target chaining error, often in the first few minutes. The usual cause is damage in one of the source files. You cannot merge your way past that damage; you repair the file first.

What target chaining means

QuickBooks stores lists, such as customers, vendors, items, and accounts, in one set of internal tables. Transactions live in another set. Each transaction carries a reference to the list entry it uses. The technical name for that reference is a target. The chaining is the sequence of references that keeps the file's data connected. When a list entry is partially deleted, or a transaction is orphaned, the chain breaks. Verify Data can find the break. The merge cannot re-point the transaction safely, so it backs out.

Before you begin

Start with a backup of each company file. Use File, Save Copy or Backup, Local backup and store the copies somewhere separate from the originals. Then close every QuickBooks window and run the work in single-user mode. On a multiuser system, choose File, Switch to Single-user Mode and confirm that no other session is connected. If either file lives on a server, bring it to a local drive with the same Save Copy or Backup command. Copying the data file alone can leave its related files behind, and Verify Data on a network share can produce false problems.

Verify both files

With the first file open, choose File, Utilities, Verify Data. QuickBooks scans the file and reports either No problems found or a list of errors. If the result mentions target chaining, make a note of it. Close that file and open the second one. Run the same check there. Repeat for every source file that is part of the merge. Do not attempt the merge until every source file returns a clean result.

Rebuild the file that fails

If either file fails Verify, run Rebuild Data on that file. Choose File, Utilities, Rebuild Data. QuickBooks asks for a backup before it starts; take it. Rebuild rewrites the internal tables and tries to restore broken references. When it finishes, run Verify Data again on the same file. Do not move on to the merge until that second Verify reports no problems. If both files failed, rebuild both and recheck both.

Retry the merge

Reopen both files and retry the merge. It should pass the point where it stopped before. If it stops at a different, later error, the file damage is no longer the blocker. The new error is more likely in the merge definitions, such as list names that do not match. In our merge work, a clean Verify on both files is the gate before list matching begins.

Signs it worked

The merge completes without error. The consolidated file opens normally. A Verify Data run on the merged file returns no problems. Check a few totals you can trace, such as the bank balance, undeposited funds, or accounts receivable, against the two source files. Keep the originals and backups until you have compared those numbers.

When this workaround is not enough

Verify Data and Rebuild Data cannot repair every kind of target chaining damage. If the same file fails again after Rebuild, the broken reference may sit in a part of the file those utilities cannot reach. At that point the file needs a specialist repair, not a retry. That is where a QuickBooks Desktop file repair service comes in. The technical detail of why the merge behaves this way is in our explanation of how merging QuickBooks company files works. The merge itself cannot fix a damaged source file; it only moves data between files.