Migrate from OneSuite to HubSpot

OneSuite contacts map directly to HubSpot Contacts. Email, phone, job title, and address fields carry over without transformation. OneSuite's contact social URLs (facebookUrl, linkedinUrl, twitterUrl) become HubSpot custom string properties. Owner resolution uses email match against HubSpot users — unmatched contacts receive a fallback owner flagged in the pre-migration audit.

OneSuite companies map to HubSpot Companies with direct field-to-property mapping for name, domain, industry, employee count, and annual revenue. OneSuite's annualRecurringRevenue and icp boolean fields become HubSpot custom number and boolean properties. Parent-company relationships (via hs_parent_company_id in the API) map to HubSpot's parent company association.

OneSuite's flat leads object maps to HubSpot Leads. Lead status and source fields from OneSuite become HubSpot Lead Status and Lead Source pick-list properties. OneSuite's lead custom fields migrate as custom properties on the HubSpot Lead object. Leads with no OneSuite lifecycle concept get a default lifecycle_stage value post-migration.

OneSuite deals map to HubSpot Deals. The deal name, amount, close date, and stage migrate directly. OneSuite's single pipeline becomes a HubSpot pipeline — if multiple OneSuite pipelines exist in the account they map to separate HubSpot pipelines. Stage names translate via a value-by-value mapping defined in the migration plan before the full run.

OneSuite projects have no native HubSpot equivalent. We create a HubSpot custom object named 'Project' with properties for project name, status, start and end dates, associated client (linked to the Company or Contact), budget, and owner. The project-to-client association migrates as a HubSpot association between the Project custom object record and the relevant Company or Contact record.

OneSuite invoices store invoice number, amount, currency, issue date, due date, status, and linked client. HubSpot has no native invoice object — we create a custom object with these fields plus a currency code property. Invoice-to-client links become HubSpot associations between the Invoice custom object and the relevant Company or Contact record. Invoice PDF files are re-uploaded to HubSpot's file storage and linked as attachments on the Invoice record.

OneSuite documents store file references, names, and document type. Files migrate to HubSpot Files (retaining original filenames and upload timestamps). A Document custom object in HubSpot holds metadata — document name, type, linked contact or company, and a HubSpot file URL — so your team can reference the document from within the CRM record.

OneSuite's API returns custom fields as flat slugs on each entity (e.g. field-slug-1, field-slug-2). During migration planning we identify each slug, infer its data type from the stored values, and create a corresponding HubSpot custom property before the data load. Pick-list custom fields in OneSuite require value-by-value translation in HubSpot's property settings.

OneSuite's accountOwnerId on companies and deals references a OneSuite user. We match OneSuite owner email addresses against HubSpot user email addresses. Matches create a direct Owner link in HubSpot. Unmatched owners are flagged in the pre-migration audit — your team either invites them to HubSpot first or assigns a fallback owner before the migration run commits.

OneSuite stores activity records (calls, emails, notes) with timestamps and owner attribution. These migrate as HubSpot engagement events — emails as email logs, calls as call engagement records, notes as HubSpot notes — attached to the relevant Contact, Company, or Deal record. Original timestamps and owner IDs are preserved so the engagement timeline in HubSpot reflects the full activity history.

OneSuite's client portal configuration — portal access levels, white-label settings, and client-facing branding — has no HubSpot equivalent. These are destination-side configuration decisions that your team configures in HubSpot's portal settings after migration. We document the current OneSuite portal configuration as a reference so your admin can apply equivalent settings.

OneSuite workflows, sequences, and task-automation rules do not migrate. They must be rebuilt in HubSpot's automation tools (Workflows, Sequences, and the Automation editor). We export your OneSuite workflow definitions as a structured reference document that your HubSpot admin can use as a rebuild specification. Automation logic that references OneSuite-specific objects (e.g., invoice-status triggers) requires redesign in HubSpot's logic model.