Migrate from improveit 360 to Salesforce Sales Cloud

improveit 360 leads map directly to Salesforce Lead records. Fields including name, email, phone, company, lead status, and source are migrated as-is. Owner resolution happens by email match to Salesforce User records before insertion — unmatched owners are flagged and assigned to a fallback user.

improveit 360 eLead records represent incoming web inquiries with routing status and source tracking. If an eLead has been worked (status 'Working' or later), it qualifies as a Salesforce Lead. Unworked eLeads that represent raw form submissions are flagged with a custom field for Salesforce admin triage rather than bulk-loading unqualified records.

improveit 360 companies migrate to Salesforce Account records. The company name maps to Account.Name, domain to Website, industry to Industry (value-mapped), employee count to NumberOfEmployees, and annual revenue to AnnualRevenue. Parent-child company hierarchies use the Salesforce ParentId field. Address components (street, city, state, postal code, country) map to the corresponding BillingAddress fields on Account.

improveit 360 contacts map directly to Salesforce Contacts. All standard fields (name, email, phone, title, address components) are migrated. Because Salesforce requires Contact.AccountId, the parent Account must exist before Contacts are inserted — we sequence Accounts first in the migration run order.

improveit 360 opportunities map to Salesforce Opportunity records. The deal name, amount, and close date are direct mappings. Pipeline-to-RecordTypeId mapping assigns each improveit 360 pipeline to a Salesforce Sales Process tied to a record type, and stage values are mapped value-by-value per record type with probability and forecast category reapplied.

Each improveit 360 pipeline becomes a Salesforce Sales Process keyed by a record type. Pipeline stages map to Opportunity StageName values per record type. Teams with five improveit 360 pipelines end up with five Salesforce record types — each requiring its own page layout, field-level security, and profile assignment before data lands.

improveit 360 stores project budgets, line-item estimates, and schedule dates as native fields. Salesforce Sales Cloud has no standard project object. We create a custom Project__c object with fields for estimated_budget__c, line_items__c, start_date__c, and completion_date__c, linked to the parent Opportunity via a lookup relationship.

improveit 360's custom fields (remodel_type__c, trade_category__c, coverage_area__c, etc.) migrate to Salesforce custom fields with __c suffix on the equivalent standard object. Field type is preserved — pick-lists become pick-lists, dates stay dates, numbers stay numbers. All custom fields are created in the target org before the migration run.

improveit 360 appointment records (with scheduled date, time, assigned rep, and result status) map to Salesforce Event records. Original start/end times, owners, and the parent-record link to the related Contact or Opportunity are preserved. Appointment result notes migrate as Event description.

improveit 360 call logs and activity records map to Salesforce Task records. The activity type (call, email, note) is stored in the Task.Type field. Original timestamps, owners, and subject lines are preserved, with the Task linked to the parent Contact, Lead, or Opportunity record.

Documents and attachments stored in improveit 360 are downloaded and re-uploaded as Salesforce Files (ContentDocument / ContentVersion). File size limits apply — Salesforce default caps at 25MB per file. Inline images embedded in notes are extracted and rehosted separately, and large files exceeding the limit are chunked or linked via external storage references to maintain document accessibility.

improveit 360 quote documents and line-item pricing tables have no direct Salesforce equivalent without CPQ. We preserve quote data as custom fields on Opportunity (quote_amount__c, quote_date__c, quote_valid_until__c) and export the line-item structure as JSON for rebuild in Salesforce CPQ by your admin after migration.