Migrate from Sentian Solutions to HubSpot

Sentian Solutions contact records (name, email, phone, company association) map directly to HubSpot Contacts. Email serves as the primary deduplication key, with duplicate detection based on exact match. Contacts lacking an email address are imported with an alternative identifier stored in a custom field (e.g., Alt_Contact_ID__c) for manual review and subsequent merge if a valid email is later identified.

Sentian Solutions company or facility records map to HubSpot Companies. HubSpot's domain-based auto‑match feature links contacts to the correct company by email domain, and parent‑child hierarchies in Sentian Solutions translate to HubSpot's parent company field. If multiple facilities share the same domain, a custom property (e.g., Facility_ID__c) preserves the distinction.

Sentian Solutions device or asset records have no direct HubSpot equivalent. We create a HubSpot Custom Object (e.g., 'Device__c' or 'Asset__c') with fields for device ID, type, location, and status. The Custom Object associates to the HubSpot Contact or Company that owns the device.

Sentian Solutions tickets or maintenance issues map to HubSpot Tickets. HubSpot Ticket properties (subject, status, priority, pipeline) capture standard ticket fields, while custom properties such as device ID, failure code, resolution notes, and internal priority tiers migrate as custom ticket properties. Multi‑pipeline scenarios in Sentian Solutions are represented as separate HubSpot ticket pipelines with stage‑level value mapping.

Sentian Solutions operational logs and time-series sensor data do not map to standard HubSpot CRM objects. High-value logs (maintenance history, alert summaries) can be stored as a Custom Object or as Notes on the associated Device or Contact record. Raw time-series data requires a separate IoT analytics platform.

Sentian Solutions owner or assignee fields resolve by email match against HubSpot Users. When an email lookup fails, the record receives a fallback assignment to a designated HubSpot user or remains unassigned, and a custom field (Original_Owner__c) records the original owner identifier for audit and later manual reassignment. All resolution outcomes are logged for reconciliation.

If Sentian Solutions tracks customer status (Prospect, Active, Churned, etc.), these values map to HubSpot lifecycle stages. 'Active customer' maps to 'Customer'; 'Churned' maps to 'Evangelist' or a custom lifecycle value per your specification. HubSpot's marketing-contact flag does not apply unless you configure marketing-only contact logic post-migration.

If Sentian Solutions tracks sales opportunities alongside operational accounts, those records map to HubSpot Deals. HubSpot deal fields (name, amount, stage, close date, pipeline) map directly. Multiple pipelines in Sentian Solutions map to separate HubSpot deal pipelines with stage-name value mapping per pipeline.

Sentian Solutions file attachments (maintenance reports, device manuals, photos) re-upload to HubSpot Files and attach to the corresponding Contact, Company, or Device record. HubSpot Files have a 250MB per-file limit. Inline images in notes are extracted and rehosted as HubSpot-hosted assets.

Sentian Solutions custom fields on any object (contact, company, ticket, device) require HubSpot custom properties created before migration. Field types are mapped: text to single-line text, numbers to number fields, dates to date pickers, pick-lists to single-option or multi-option properties. Required-field constraints in HubSpot are validated post-migration.