Migrate from solve 360 to HubSpot

Solve 360 contacts migrate directly to HubSpot contacts. The primary company association maps as a Contact-Company association in HubSpot. All standard fields (name, email, phone, job title, address) move as direct field mappings. Solve 360 owner resolution occurs by email match against HubSpot user accounts before contact records are created.

Solve 360 companies map 1:1 to HubSpot companies. Company name, domain/website, industry, employee count, and annual revenue move as direct or value-mapped fields. Parent-child company hierarchies in Solve 360 map to HubSpot's company associations model using the same relationship type.

Solve 360 task types (call, email, follow-up) map to HubSpot engagement types by subject and body content. Original timestamps, task owners, and associated contact and company IDs are preserved. Task status (open, completed) maps to a HubSpot custom property since HubSpot's engagement model tracks completed activities only.

HubSpot meeting engagements store start time, end time, location, and body. Solve 360 calendar events migrate with original timestamps and owner preserved. Meeting body and title map to HubSpot meeting title and description. Attendee list from Solve 360 maps to HubSpot contacts associated to the meeting engagement.

Solve 360 notes attached to contacts or companies migrate as HubSpot engagement notes. Rich-text formatting is preserved where possible. Notes without a specific association in Solve 360 are attached to the contact record as general notes on the HubSpot contact timeline.

Any Solve 360 custom fields on contact records that do not match HubSpot's standard contact properties require pre-creation as HubSpot custom contact properties before migration. We deliver a custom-field creation plan listing each Solve 360 field name, data type, and recommended HubSpot property type before data moves.

Solve 360 company‑level custom fields are mapped to HubSpot custom company properties, created before migration. Multi‑select pick‑lists become HubSpot checkbox or multiple‑checkboxes properties, with cardinality determining the type. Single‑select pick‑lists translate to HubSpot radio‑button or select properties, and boolean flags map to single‑checkbox properties. Date and numeric fields are stored as HubSpot date or number properties, preserving the original format.

Solve 360 time records attached to tasks or events do not have a HubSpot native equivalent. We migrate time-tracking duration as a custom numeric property on the associated deal or contact record, labeled Time_Tracked_Minutes__c, so reporting continuity is maintained in HubSpot custom reports.

Solve 360 workflow automations — assignment rules, stage triggers, notification sequences — do not migrate because HubSpot's workflow engine uses different trigger types, conditions, and action blocks. We export workflow definitions as a JSON reference document for HubSpot's workflow builder, listing each workflow name, trigger, conditions, and actions for your team to recreate.

Solve 360 contact and company tags map to HubSpot contact and company properties. We create a tag-string property in HubSpot populated with the Solve 360 tag values. If tags are used for segmentation, the rebuild in HubSpot can use list membership based on these property values.

Solve 360 file attachments on contacts or companies are downloaded and re-uploaded to HubSpot Files, then linked back to the contact or company record. File size limits on HubSpot's platform apply (25MB per file). Inline images in notes are extracted and hosted separately.

Solve 360's Gmail add‑on rules, which automatically create contacts or log emails based on sender or subject conditions, have no direct counterpart in HubSpot. The rule logic, triggers, and actions are exported as a reference document for your team. HubSpot's Gmail integration must be installed and reconnected to the same inbox, and any desired automation—such as auto‑contact creation or email logging—must be rebuilt using HubSpot's workflow builder or the CRM inbox settings.

Solve 360 calendar entries that originated from Google Calendar sync do not transfer as linked events. HubSpot's meeting scheduler creates separate meeting links and records. Calendar event history migrates as meeting engagements with original timestamps but the Google Calendar link is severed.