@Rhonda Budvarson and @JD Cowell This is definitely a new problem in the old merge. I wonder if needed adjustments in the old merge as part of preparation for rolling out the new merge wrecked the way marriages are handled in the old merge.

JD, I did go ahead and test this out by reversing the merge you did and looking at various configurations. Then completed the merge again, making sure I didn't actually change anything. Here is what I found. (Margaret is the wife of my 9th cousin so it seemed fine to tinker.)

Using the old merge, you have the three page process. First the initial overview:

The the page where you can choose which information to use:

Since the one Margaret has no couple events, there is nothing to even consider moving over. However, when you go to the next page to see the effects of the merge:

you can see that the "no couple event" was automatically moved over, erasing the relationship to Charles. This should not be happening.

You can see in Merge View for the original merge JD completed that the same thing happened and Charles vanished during the merge:

Before completing the merge, I went back to the second page and reversed positions:

This time, Charles was automatically moved over and the third confirmation screen shows this:

Ironically, the new merge which has had it's own problems managing couple events (I haven't had the opportunity to have a merge and see if there has been progress with those yet), handles this situation just fine. Here is the merge in one direction:

And in the other:

In both of these Charles comes over without any problem. I used the first version to complete the merge which is the direction in the old merge that lost Charles and the merge when just fine.

This problem really needs to be fixed in the old merge so couple relationships are not lost all over the place during the trial and roll out phase for the new merge.