As content and dependencies are cloned, Admin Tools prevents duplicates by looking for items in the target that share the same EXACT title and owner. If the tools find them, the cloning logic will attempt to wire the dependencies to it.
While this both necessary for the cloning operation ( to prevent moving a layer or map multiple times if it is referenced by multiple parent items), it is also intended to save time. Time can be saved using this by moving larger services in small groups BEFORE moving webmaps that rely on the services.
Note
If you want to save time by manually standing up your feature services or map services, the cloning logic will allow for this.
Related articles