Migrate from Assured JobCheck to Salesforce Sales Cloud

Assured JobCheck Job records map to Salesforce Case objects representing restoration work orders. Case.Status maps from Job stage, Case.Subject holds the job name, and Case.Account links to the insurance carrier or property owner Account. If revenue tracking is primary, Jobs map to Opportunity instead — your admin chooses per pipeline.

Claim records — storing adjuster name, loss type, policy number, and reserve amounts — merge into the parent Case as custom fields (Claim_Policy_Number__c, Claim_Adjuster__c, Claim_Loss_Type__c, Claim_Reserve__c). We preserve the Claim object's original create date as Original_Claim_Date__c for continuity in insurance reporting.

PackOut-integrated Contents lists map to a custom Contents_Line_Item__c object with a lookup to the parent Case. Fields include Item_Name__c, Room__c, Barcode__c, Condition__c, and Status__c. The N:N relationship between Jobs and Contents translates as CaseId on the line-item custom object, and each Contents item retains its original barcode value for inventory continuity.

Contact records — property owners, insured parties, adjusters — map 1:1 to Salesforce Contact. We preserve the Contact's primary Company association as AccountId. For adjuster contacts who are also Salesforce Users, we match by email and set the OwnerId accordingly.

Insurance carriers, property management companies, and vendor businesses stored as Companies in JobCheck map to Salesforce Account. Company.industry maps to Account.Industry, and company phone/fax map to Account.Phone and Account.Fax. Multi-address companies preserve the primary address as BillingAddress on the Account record for accurate invoicing and shipping purposes.

Field crew assignments and task checklists in JobCheck migrate as Salesforce Tasks attached to the parent Case. Task.Subject holds the assignment description, Task.Status tracks completion, and Task.ActivityDate stores the due date. Original crew assignment (owner) resolves by email match to Salesforce Users.

Photos uploaded via the mobile app to JobCheck photo folders re-upload to Salesforce Files (ContentDocument/ContentVersion). We preserve folder structure as ContentWorkspace libraries, and inline images in job notes download and rehost as Salesforce Files attached to the parent Case for complete documentation continuity.

JobCheck stores owner IDs referencing internal users. We resolve each owner by email match against the destination Salesforce org's User records. Unmatched owners are flagged for your admin to invite to Salesforce or assign to a fallback User before migration commits.

JobCheck's custom workflow engine — including stage-advance triggers, assignment rules, and notification logic — does not migrate. We export your workflow definitions as a reference document so your Salesforce admin can rebuild equivalent logic in Flow Builder and Process Builder post-migration.

JobCheck dashboards and saved reports covering job profitability, owner performance, and referral tracking do not transfer. The underlying data migrates, but reports and dashboards must be rebuilt in Salesforce Reports & Dashboards or Tableau CRM. We provide field-level mapping so your admin can reconstruct report filters.

Real-time team updates and internal communications stored in JobCheck's Job Feed migrate as Salesforce CaseComments or Chatter FeedItems on the Case. Original timestamps and author names (resolved by email match) are preserved. External customer-facing emails route through Salesforce Email-to-Case or Case_comments.