Switching from CompanyCam

Choose an import method

An owner or admin can open Settings → Photo documentation → Open switch kit.

• Choose CompanyCam API for a full account migration. Paste the token for the active batch. JobsiteOn does not save the token, so you must enter it again after a browser refresh.
• Choose ZIP export if you have a CompanyCam takeout archive. The ZIP can be up to 250 MB and must contain manifest.json at its root. JobsiteOn processes it only after the file scan reports clean.

If CompanyCam shows account totals, enter the expected project and photo counts before starting. That gives the completion validator a source-of-truth number instead of treating a partial copy as success.

Resume safely

API imports checkpoint after each project page. A paused or failed run can be resumed with the same row in Import history. Source IDs make each imported project and photo idempotent, so a retry does not create another copy of work that already finished.

The details drawer shows each source project, imported and failed photo counts, and any item that needs review. Fix the source problem and resume when possible. Some failures, such as a photo for which CompanyCam did not return an original URL, require a manual export.

Validate before cancelling CompanyCam

A successful run compares imported totals with the expected counts you entered. Treat either count mismatch or any failed item as unfinished migration work.

Before retiring CompanyCam:

1. Confirm project and photo counts match.
2. Open representative older and newer projects.
3. Check original capture dates, location where available, notes, and several full-size photos.
4. Keep the CompanyCam export until your retention policy allows it to be removed.

JobsiteOn computes an immutable content hash for imported originals and keeps the CompanyCam source identity in the import ledger.