Migrate from OptifiNow to HubSpot

OptifiNow Leads migrate as HubSpot Contacts. HubSpot uses lifecycle_stage as the progression property — we set the initial lifecycle_stage value based on OptifiNow's lead status field during the mapping phase. Original owner assignments resolve by email match to HubSpot users.

Direct 1:1 map. HubSpot's Contact object holds all standard contact properties (name, email, phone, address). If the OptifiNow contact has no associated Account, it lands in HubSpot as a Contact without a Company association — a default placeholder company can be assigned or left unlinked per your rule.

OptifiNow Accounts map directly to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue fields migrate to HubSpot's standard Company properties. Parent-account hierarchies in OptifiNow translate to HubSpot's parent company association on the Company record. All account associations are preserved during migration to maintain your organizational data relationships intact.

OptifiNow Opportunities map to HubSpot Deals. Each OptifiNow deal carries a pipeline name and stage; we translate these to HubSpot's Sales pipeline model, creating a HubSpot pipeline with matching stage names. Deal amount, close date, owner, and custom properties move to HubSpot Deal fields.

OptifiNow pipelines are named configurations that define the available stages for Opportunities within a team or business unit. Each OptifiNow pipeline becomes a separate HubSpot Sales pipeline. Stage order and names map 1:1; if HubSpot's default stages don't match, we add custom stage names to the target pipeline before the deal migration runs.

OptifiNow's named lead stages (Lead, Prospect, Nurture, Qualification, etc.) have no direct HubSpot equivalent because HubSpot uses a fixed lifecycle_stage pick-list. We create a Lifecycle_Stage__c custom property on the Contact object and map OptifiNow's stage names to the closest HubSpot lifecycle_stage value — unrecognized stages default to 'Lead' and are flagged for your admin to confirm.

OptifiNow engagement records — calls, emails, meetings, and notes tied to a contact or opportunity — migrate as HubSpot Engagements. HubSpot Engagements carry the original timestamp, owner, and a link back to the parent Contact or Deal. Inline attachments in notes are downloaded and re-uploaded to HubSpot Files.

OptifiNow custom properties on Leads, Contacts, Accounts, and Opportunities require HubSpot custom properties to be created before data loads. We create the custom properties via HubSpot's API during the schema setup phase, using the OptifiNow property type to infer the correct HubSpot field type (string, number, date, picklist, etc.).

OptifiNow workflows and multi-step sequences define outreach logic, time delays, and branching rules that cannot be imported into HubSpot. FlitStack AI exports the workflow definitions and sequence step data as a structured document your HubSpot admin uses to rebuild the logic in HubSpot workflows and sequences.

OptifiNow integrations built for specific verticals (VOIP call matching, LOS pipeline triggers, pricing engine hooks) are proprietary API builds scoped per-customer. HubSpot's App Marketplace and API layer provide the foundation for rebuilding these connections, but the integrations themselves do not migrate.

OptifiNow content management assets — sales collateral, templates, and media files — migrate to HubSpot Files. We download the full content library from OptifiNow and re-upload to HubSpot Files, preserving file names and folder structure where it exists. Content associations to deals or contacts are preserved as metadata.

OptifiNow users and owners resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns the records to a designated fallback owner. This is critical because HubSpot Deals require a valid OwnerId on every record.