CompanyCam + Jobber: verify where your job photos actually land

The short answer

Before adding another photo system, decide whether a property-level photo folder is enough or whether each separate service job needs its own evidence trail. CompanyCam offers Legacy, which routes through one project per property, and Lifecycle, which adds projects for separate Requests, Quotes, and Jobs. A conversion within one work thread is not a separate job. Test where each image lands before buying around either model. CompanyCam's connection guide explains the setting; its behavior guide describes the record transitions.

Unresolved official conflict: Jobber's CompanyCam article says videos are unsupported and gives a 50 MB maximum, while CompanyCam's August 2026 article includes videos among synced media. These statements cannot establish support for your exact account. Ask both vendors about the current plan, configuration, media type and size, then test only in an authorized sandbox. Do not rely on video for the job record until this gate is resolved.

Pick the record you actually need

CompanyCam says existing connections remain on Legacy, new connections start on Lifecycle, and reconnecting switches to Lifecycle. Confirm the selected mode again after any reconnection. The integration is limited to select plans and setup permissions; Project Groups and Jobber custom fields have separate plan conditions. Check your exact account rather than inferring eligibility or price here. Source: CompanyCam setup and mode documentation.

One fictional property, two separate jobs

Use a made-up property called Cedar House, with synthetic records and images bearing harmless markers such as CEDAR-A-01. First create Request A for a maintenance visit, add an image, convert A to Quote A and then Job A. Next create Job B as a separate, unrelated visit at the same property, and add image CEDAR-B-01. Keep both Job IDs and the CompanyCam project IDs in a ledger. The question is whether B's image appears only on B in Lifecycle, while A's earlier evidence remains retrievable through the intended note link. In Legacy, check the currently active destination instead of assuming a permanent separation. This is a proposed test, not an observed result.

CompanyCam says old notes need to be linked to related records before conversion if you want existing attachments to carry forward; new media after conversion has a different routing rule. Neither connecting the integration nor changing modes proves a complete historical import. Existing projects and older records may need vendor-assisted historical sync or their own verification. Pages and Checklists are not the same automatically synced objects as media: an exported PDF saved as a file is a separate route. Source: CompanyCam workflow and FAQ.

Eight checks to record before a decision

Run only with permission, in a test environment, using synthetic images with no personal data. Never connect a real customer account or create production jobs to complete this article. For each row, capture the selected mode, account plan, record IDs, timestamp and the actual destination. Leave the last column blank until you perform your own authorized test.

If images land on the wrong Job, stop the trial and trace mode, project label, linked Job URL and the note's timestamp. Do not solve a mismatch by erasing old evidence. If historical notes, file limits or videos are important, obtain written clarification and a reproducible account-specific result before committing to a workflow.

Keep the buying question narrow

This is an integration routing test, not a general proof-of-service app comparison. For Jobber's complete intake-to-invoice sequence, use our Jobber workflow test and Jobber evidence review. If the next visit is waiting on a physical part, follow the separate parts-on-hold workflow. No CompanyCam affiliate relationship is confirmed for this guide, and no referral link or score is offered.