We are testing Courier in a non-production environment and running into an issue with the tree location of copied nodes.

Courier successfully moves content from the source to the destination system, but it does not seem to recognize when a higher-level container node already exists, and instead places copied nodes into (seemingly) unpredictable locations in the tree.

For example, in the below source structure, the Level3 node and its children are to be transferred to the target server:

Content

->Level1

----->Level2

---------->Level3 (this node and it's children are transferred)

On the target server, the below structure is created (Level1, Level2 and Level3 nodes exist on target server before transfer):

Content

->Level1

----->Level2

---------->Level3 (this Level3 node already exists on target) *

---------->Level3 (this Level3 node was transferred from source) *

* The Level3 node is a dateFolder document type containing multiple dateFolder children and a blogpost as the final element.

In the above example, Courier created the new node at the appropriate level in the tree, but did not recognize that a node with the same name already existed.

In other tests, Courier has sometimes created new nodes at the top level of the tree, under Content.  I have not detemined the pattern for where in the tree nodes will be created.

Any insight into this would be greatly appreciated.

Thanks!

Jeff