Migrate from Contractor+ to Salesforce Sales Cloud

Contractor+ Clients map directly to Salesforce Accounts. Company name maps to Account.Name. Domain and address fields map to Account Website and address compound fields. Parent-child company hierarchies in Contractor+ map to Account.ParentId — circular references are flagged before migration runs.

Named contacts on a Contractor+ Client become Salesforce Contacts linked to the Account via AccountId lookup. Contractor+ allows multiple contacts per client; Salesforce supports this via the same model. Primary contact designation migrates as a custom Is_Primary__c flag. All contact details such as phone, email, and title transfer directly to the corresponding Salesforce Contact fields.

Contractor+ Leads that are not yet converted to Clients map to Salesforce Leads. Lead status pick-list values require value-by-value mapping to Salesforce Lead Status. Unconverted Leads with existing phone/email data preserve those fields on the Salesforce Lead record. Ensure any custom lead sources are mapped to the appropriate Salesforce LeadSource pick-list entry.

Contractor+ Jobs are the core work record and map to Salesforce Opportunities. Job name becomes Opportunity Name. Job status (scheduled, in-progress, completed) maps to StageName via value mapping. Contractor+ allows one Opportunity per job — complex multi-phase jobs may need multiple Opportunities or a custom Job_Phase__c field.

Contractor+ Estimates do not have a direct Salesforce equivalent at this tier. FlitStack creates a custom Estimate__c object with fields for estimate number, total amount, status, and a lookup to the Opportunity. Line items from the estimate become Estimate_Line_Item__c records linked to the Estimate__c parent.

Contractor+ Invoices store full billing records — these have no native Salesforce equivalent. FlitStack creates a custom Invoice__c object with invoice number, amount, status, date, and a lookup to the Account. Paid invoices preserve payment date and amount; unpaid balances surface as open receivables.

Contractor+ line items on estimates and invoices map to a custom Line_Item__c object. Each record stores description, quantity, unit price, and total. The line item links to the parent Estimate__c or Invoice__c via a lookup field. Material codes and labor rates from Contractor+ preserve as custom text fields.

Contractor+ Team Members resolve to Salesforce Users by email match. Unmatched team members are flagged before migration — your team either invites them to Salesforce first or assigns their records to a fallback owner. Contractor+ role flags (admin, technician, dispatcher) map to Salesforce Profile or Permission Sets.

Any custom properties stored on Contractor+ Clients, Jobs, or Estimates become Salesforce custom fields with the __c suffix. Pick-list custom properties require value-by-value mapping to Salesforce pick-list values. Rich-text custom properties preserve formatting in long-textarea fields. Field-level security settings should be configured after migration to control visibility across user profiles.

Contractor+ file attachments on Jobs or Clients re-upload to Salesforce Files linked to the corresponding Opportunity or Account. File size limits apply (Salesforce default 25MB per file). Inline images in notes are downloaded and rehosted in Salesforce's secure storage. Consider reviewing file access settings post-migration to align with sharing model requirements.

Contractor+ notes on Jobs or Clients migrate as Salesforce Notes (not the legacy Note object) attached to the parent Opportunity or Account. Original timestamps and author information preserve in the Note record so project history is auditable post-migration. These notes remain searchable within Salesforce after the transition.

Contractor+ workspace memberships grant team members access to clients and jobs. These map to Salesforce AccountTeamMember on Accounts and OpportunityTeamMember on Opportunities — your admin configures which roles map to which team member roles before migration runs. Review the team member role assignments in Salesforce after migration to ensure appropriate record-level visibility.