What you are seeing is two different sets of data, and only one of them survived the move.
The meshes that show up in the right places on the other PC are the generated output, serialized in the level. The paint tool does not edit those meshes. It edits the tool data (the stroke / point set) on the PCG component, then on Accept it regenerates the output from that set and deletes whatever it previously generated. Copy, Migrate, and Convert to Level all copied the output. They did not bring a usable copy of the tool data, which matches your read that the strokes live with the level rather than in their own asset.
That is also why both buttons wipe the level. On the new machine the tool opens an empty stroke buffer. Accept writes that empty buffer back and the component cleans up the generated meshes. Cancel restores the tool data, which is also empty, so the same cleanup runs. Until the strokes are actually loaded, do not press either button or you will delete the only copy of the result you still have.
On the original computer, while the paint tool still has the strokes:
Select the generated meshes and bake them out if you only need the result: merge them to static mesh actors, or pack them into a packed level actor, and migrate those. They will no longer be owned by the PCG component, so a later Accept cannot delete them.
If you need the strokes to stay editable, the tool data has to be a real asset, not inline data on the actor. From the paint tool or the graph input, export the points to a PCG data asset if that action is available, save it, and migrate that uasset together with the PCG graph. On the other project, point a PCG component at that data asset and generate from it. Inline tool data does not survive actor copy or Migrate.
Also copy the level’s external actor folders, not just the umap. For a level that uses external actors, the component and its tool data are often in Content/ExternalActors and Content/ExternalObjects under that level’s guid. Migrate of the single actor, and copy-paste, both skip those packages. Copying only the umap leaves the generated meshes (they got embedded) and drops the strokes.
Merging two machines is the same constraint. You cannot paste the actor both ways and keep the paint editable. Bake or export on each side, migrate the assets, and regenerate. Copying the whole project folder would have worked only because it includes the external packages and the unsaved-in-asset level package together.