Importing a Katapult model is a sequence you cannot skip around in. Each step stays locked until you finish the one before it, and each step also locks once you confirm it, so there is no stepping back to change your mind. That makes twenty minutes of preparation worth more here than on most things, because the alternative is deciding in the middle.

The name is the one decision to treat as permanent, so have it settled before you begin. Once you confirm it, the import will not let you change it.

Administrator access to your Cloneable organization. The import page checks this before anything loads, so without it you get a message telling you that you do not have permission to create or edit configurations, and an empty screen. If someone from Cloneable helps you, your organization needs to give them that same access. Working for Cloneable is not a substitute.

Your own Katapult sign-in, with access to the model you want to bring across. Cloneable reads the model as you, so if you cannot open it in Katapult, neither can we.

Google Chrome, with the Cloneable extension added. See Add the Cloneable extension to Chrome.

Your model already sent across. The import page consumes what the extension has collected, so nothing appears until you have run the export. If the page tells you to use the extension when you know you already have it, that means no model has arrived yet. More on that.

A name, in the format the screen accepts. Only letters, numbers and underscores. Spaces get turned into underscores whether you meant it or not. It also has to be a name no other configuration in your organization uses. The screen checks while you type and will not let you past the first step until the name is free. Cloneable can refuse a name an earlier configuration used, too, if that configuration left templates behind when it was deleted. The import also attaches the name to the end of every template it creates, so it is how you will tell this configuration's poles from another's later. Q1_2024 and Project_Alpha are the shapes the screen itself suggests. Name it after the work, not the day you did it.

Your measurement unit. Metric, feet and inches, or feet as a decimal. It is required at the first step and it is what your crews will see on their phones, so pick what they say out loud and what your engineers expect to receive.

Whether you need ground line circumference. There is a checkbox for it at the first step. It gives whoever reviews poles in the office a measuring tool on the photo.

Which parts of the model actually matter. You will choose from your model's node types, connection types and pole annotations. Worth knowing roughly which ones your crews use before you look at the whole list at once.

What your crews genuinely need to fill in. The heaviest decision in the whole sequence is which attributes to keep, because every one you include becomes a field somebody reads on a phone in the sun. A type can carry sixty. Have a view before you get there.

Which photos you expect. Attributes include photo slots, and one anchor type offered twenty-four. Decide what your crews are actually required to photograph.

We often put that list in a workbook: fields, photos, and dropdown versus free text. You check it off with us on a call. The wizard is where you pick what comes across. The workbook is not a file you import.

Do this before you start the import, not after. You have to save your Katapult API key in Cloneable, in your Secrets Vault, before you bring your model across.

Here is why the order matters. Step 6 of the import asks you to choose an import trigger and an export trigger, which are the two automations that move jobs out of Katapult and finished work back into it. We set those up against your stored key, so if the key is not there yet, there is nothing for you to choose at that step.

Storing it takes a few minutes and it is the one thing worth doing before anything else. How to store it.

The same credential is what lets you create jobs that pull from Katapult later. If it is missing, creating a job fails with an error about loading jobs that mentions neither Katapult nor credentials. How to fix that.