Migrate from solve 360 to Salesforce Sales Cloud

Solve 360 Contacts map to either Salesforce Lead or Contact depending on the relationship context at migration time. Unqualified or loosely affiliated contacts with no active Opportunity map to Salesforce Lead. Contacts with a linked Company that represents a sales-ready account map to Salesforce Contact tied to an Account. We resolve the split by checking the Solve 360 record for active Deals, Support Requests, or follow-up status. Original Solve 360 contact properties (email, phone, title, lifecycle indicators) migrate as typed Salesforce fields or custom fields for audit.

Solve 360 Company records map directly to Salesforce Account. Company name becomes Account Name, domain maps to Account Website, and address fields map to Billing Address. Account is created before any Contact import so the AccountId lookup is satisfied at the moment of Contact insert. Multiple Solve 360 Contacts linked to the same Company consolidate under a single Account parent.

Solve 360 Tasks map to Salesforce Task with Status, Priority, ActivityDate, and description preserved. Time entries attached to tasks migrate as a custom time-tracking field on the Task record. Task assignment resolves Solve 360 owner IDs to Salesforce OwnerId via the User mapping. Status values map to Salesforce Task Status (Not Started, In Progress, Completed, Waiting on Someone Else).

Solve 360 Follow-ups are time-stamped activity records tied to a Contact or Company. Follow-ups with a specific scheduled time and duration map to Salesforce Event (StartDateTime, EndDateTime, Location preserved). Follow-ups that represent a to-do without a set time map to Salesforce Task. Attendee context from the Follow-up links via EventRelation records if migrating as Event. The original Solve 360 Follow-up type label is preserved in a custom field for reporting.

Solve 360 Support Requests track issue lifecycle from open to resolution against a Contact or Company. We map Support Requests to Salesforce Case if the destination org includes Service Cloud. If the destination is Sales Cloud only, Support Requests migrate as a custom object (Support_Request__c) with Status, Priority, Description, and linked Contact preserved as custom fields. The customer selects the strategy during scoping. Full conversation history migrates as EmailMessage records linked to the Case.

Solve 360 Time Records attach to tasks, site notes, calls, and meetings with duration, date, billing flag, and associated parent object. We export time entries and re-attach them to the parent Task record in Salesforce using a custom Duration_Minutes__c field and a Billing_Entry__c checkbox. If the destination org uses a time-tracking app from the AppExchange, we deliver the time data as a CSV import file alongside the Salesforce native migration.

Solve 360 pipeline configurations (stage names, order, probability percentages) export and become Salesforce Sales Processes on Opportunity. Each Solve 360 pipeline maps to a Salesforce Record Type with a corresponding Sales Process that whitelists the stage values. Stage probabilities map to StageProbability on OpportunityStage. If no Opportunities exist in Solve 360, we still create the Sales Process configuration for future use.

Solve 360 Users are both system actors and assignment targets on Tasks, Follow-ups, and Support Requests. We export the full user list and map owner IDs to Salesforce User IDs by email match. Any Solve 360 owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Ownerless records are flagged for manual assignment post-migration.

Solve 360 user-defined custom fields on Contacts and Companies map to typed Salesforce custom fields on the equivalent destination object. Field types (text, number, date, selection) map to Salesforce Text, Number, Date, and Picklist fields respectively. We pre-create the destination custom field schema in a Salesforce Sandbox before production migration. Selection field values map to Salesforce Picklist values on the target object.

Solve 360 Tags label Contacts, Companies, Tasks, and Support Requests. We export all tags with their record associations and re-apply them as Salesforce native Tags (TopicAssignment records on Contact and Account) or as a multi-select picklist custom field on the target object. The customer selects the tag strategy during scoping based on whether they want taxonomy-style tagging or label-style classification.

Attachments on Contacts, Companies, Tasks, and Support Requests are downloaded from Solve 360 as files and re-uploaded to Salesforce. File metadata (name, type, size, upload date) is preserved. Files re-attach to the parent record via ContentDocumentLink (for Salesforce Files) or the native Attachment object. Very large file attachments may require chunked upload via the Salesforce REST API.

Solve 360 Workflow definitions encode automation logic specific to its engine (intelligent scheduling, assignee notification, multi-step task sequences). We export workflow configurations as structured JSON metadata for the customer's reference. Workflows cannot be directly replayed in Salesforce Flow because the trigger models and action types differ. We deliver a written Workflow Inventory document listing each active workflow, its trigger conditions, steps, and a recommended Salesforce Flow equivalent, and the customer's admin rebuilds them post-migration.

If the customer uses Solve Client Manager with custom object configurations, those migrate to Salesforce custom objects of equivalent API name with a __c suffix. We pre-create the destination schema including all custom fields, lookup relationships, and validation rules before any data import. Custom object migrations require a schema review during discovery to identify inter-object lookups that must resolve before insert.