This guide walks you through exporting a completed job from Cloneable back to Katapult. Once your fielders have finished collecting data and everything has synced to the web portal, you can trigger an export to send the data back to your Katapult project. If you haven't imported the job yet, see How to Import a Katapult Job into Cloneable first.
In This Guide
Before You Start
Make sure the following are in place before triggering an export:
All field data has synced from the mobile app to the web portal (check the sync status on each device). If you see image sync warnings, see Troubleshooting Image Sync Warnings.
Your configuration has an export trigger configured (this was set up during the initial Katapult model import)
All required fields on poles and midspans are complete
Important: Make sure all fielders have finished working in the job and their devices show "Synced" before exporting. Fielders working in a job during export should not cause issues, but it's best practice to wait until all data is uploaded to avoid partial exports.
Tip: The web portal will warn you if there are unsynced files for this job before you begin the export. If you see this warning, wait for all field devices to finish syncing before proceeding. You can check sync status on the utility map.
How to Export a Job
Log in to the Cloneable web portal
Find your job on the dashboard and click View Map to open the map view
Verify that everything from the field came in correctly: poles are collected, data is present, photos are visible
In the top left of the map view, click the Export button (the third button down)
Select Export to Katapult from the options
The system will ask you to confirm multiple times. Click Yes each time.
A status bar will appear in the bottom left of the map view showing progress and flagging any errors
Tip: Only click the Export button once. Clicking it multiple times can queue up duplicate exports, which may slow down processing.
Understanding Export Statuses
After triggering an export, you'll see one of the following statuses:
Status | What It Means |
Pending | The export is queued and waiting to process. You may see a number (e.g., "Pending 795") indicating how many items are in the queue. |
Processing | The export is actively sending data to Katapult. This can take several minutes depending on the size of the job. |
Completed | The export finished successfully. Your data should now be available in Katapult. |
Error | Something went wrong during the export. Check the error details and contact support if needed. See Troubleshooting Export Errors for common issues and solutions. |
Note: Large jobs with hundreds of poles may take longer to process. Export time can range from five minutes to a couple of hours depending on data volume and API traffic. You don't need to keep the page open; the export continues in the background.
Tip: The export status indicator may not always refresh automatically. If the progress bar appears stuck, try refreshing the page to see the latest status.
Tip: You can use conditional map styles to visually track which poles have been exported vs. not yet exported, using the last_export field.
Verifying Your Export in Katapult
After the export shows "Completed":
Open your Katapult project in the browser
Verify that the field data, measurements, and photos have been transferred
Spot-check a few poles to confirm attachment heights and field values are correct
Important: If the export status shows "Completed" but some data appears missing in Katapult, try running a re-export (see below). In rare cases, individual items may not transfer on the first attempt even though the overall status shows success.
What to Do If an Export Gets Stuck
If your export has been stuck on "Pending" for more than 30 minutes or appears to have stalled:
Do not click Export again. Duplicate exports can cause queue conflicts.
Check that your export trigger is still active in your configuration settings
Contact the Cloneable support team through the chat widget or email [email protected]
Include the job name and how long the export has been stuck so we can investigate quickly
Note: Our team can manually restart a stuck export from the backend. This does not affect your data or require any action from fielders.
For more troubleshooting steps, see Troubleshooting Export Errors.
Re-Exporting a Job
You can re-export a job at any time, even after a successful export. This is useful if:
Some data didn't transfer on the first export
Fielders made corrections or additions after the initial export
You need to update photos that were rejected by Katapult on the first attempt
To re-export, simply click the Export button again on the job. Re-exports are incremental: the system tracks what was and wasn't successfully delivered, and only sends what's missing or updated. It does not re-send all data from scratch. In rare cases, a re-export may show a success count but the data may not appear in Katapult. If this happens, refresh the page and verify the export in Katapult before closing the job.
Known Differences Between Cloneable and Katapult
Some data does not transfer automatically between Cloneable and Katapult due to API differences. Be aware of these when verifying your export:
Item | What to Know |
Pole deletions | Deletions do not push through the API. If you delete a pole in Cloneable after it has been exported, it will remain in Katapult. In some cases, previously deleted poles may re-export stale data. If you see unexpected poles in Katapult, verify their status in Cloneable and remove them manually in Katapult. |
Added poles | If you added a pole in Cloneable, verify that the two new line segments are visible in Katapult and the old single line isn't hiding behind them. |
Moved poles | If a pole was repositioned in Cloneable, verify it moved correctly in Katapult. It does not always translate perfectly. |
Connection type changes | Changes to span types (overlash vs. new attach) made in Cloneable may not carry over to Katapult correctly. Verify and update these manually. |
Field complete checkmark | Cloneable does not send the "field complete" status to Katapult. You will need to manually set this on each completed pole in Katapult. |
Photo orientation prompt | Katapult may flag every height photo and midspan photo as coming from a third-party tool and ask for approval. Click "Do It Anyway" once per type per job to accept all photos. |
Tips & Reminders
Make sure all devices show "Synced" before triggering an export
Only click Export once. Multiple clicks can cause queue conflicts.
Large jobs may take several minutes to hours. The export runs in the background.
If an export shows "Completed" but data is missing, try re-exporting
Re-exports are incremental; they only send what wasn't delivered before
Contact support if an export is stuck on "Pending" for more than 30 minutes
Always verify your export in Katapult, especially for added, moved, or deleted poles
The attributes you selected during the initial configuration import determine what gets exported. If a field isn't appearing in Katapult, check your configuration's attribute selections.