Katapult and Cloneable do not use the same words for the same things. Matching them up is one step of the import, and it is the step that decides whether a thing on your map behaves like a pole or is just a dot with data attached.

Your Katapult type names will differ from the examples here. See Why your screens may not match this guide.

Anything matched to one of these inherits everything Cloneable knows how to do with it: how it gets measured, how it connects to its neighbors, and how it exports back out.

None of the three matches is forced. Every one of these selectors offers to use defaults instead of a type from your model, and the step lets you continue either way. Its only check is the box confirming you reviewed your mappings. Anything you leave unmatched turns up in the unmapped list further down the same step, which is where you decide what happens to it.

Guy Anchor asks for one thing the others do not: an export connection type, meaning the Katapult connection your anchors go back out as. Cloneable starts this at down guy, a default of its own rather than anything read from your model. The choices offered are your model's own connection types, so check the selector shows one of them, and set it to whatever your anchors should go back out as.

Cloneable's own wording on the step:

On screen: "Map your Katapult node types to standard data objects. Unmapped nodes will be imported as custom data objects."

A custom object still appears on the map and still collects data. It will not export as a pole, and it offers no measurement at all unless you give it a measurement style, which this article covers below.

That is often exactly what you want. Notes, reference points, and guy runs are real things your crews need to see, and none of them are poles.

You do not start from an empty grid. On a full model import, Cloneable looks at the types you chose to include and matches:

Check these rather than trust them. If your model names its poles something else, the guess will not fire and you need to set it yourself. A missed pole match is the single most expensive mistake on this step, because everything about pole measurement depends on it.

Whatever is left over is listed under a plain note that these will be imported as custom data objects, split into points and lines, each with a tick box. Ticked brings it across as a custom object. Unticked means it does not come across at all.

On a fresh import they all arrive ticked, so your job here is pruning. Work down the list and ask one question of each type: do my crews need to see this in the field? If it is Katapult bookkeeping that means nothing to someone standing at a pole, untick it. You can come back and change this later.

Points get a second choice, and it is the one people miss. You can set each ticked point type to a measurement style of none, pole, or midspan. That decides what happens when a fielder opens it:

Lines do not get this choice.

Span is the cable. Midspan height lives on the aerial or overlash connection. You pick that photo slot in Select Attributes. Matching a type to Span on this screen does not place the slot. See Choose what comes across from your Katapult model.

The midspan measurement style on a custom point is a different control. It only changes how a fielder opens that point. It does not put midspan height on a span.

Fielders capture the reading with Measure a midspan (High Accuracy).

A real model came across like this:

Three matched, six brought across as custom objects. Note that the guy runs became custom lines rather than spans, because a guy is not a cable span between two poles even though it looks like a line on the map.

Match it if your crews will measure it. Bring it across as a custom object if they only need to see it. Leave it off if neither is true.