Migrate from WayMore to HubSpot

WayMore contacts migrate directly to HubSpot Contacts. Every standard property (name, email, phone, job title, address) maps to the HubSpot Contact property of the same name. WayMore's lifecycle stage property migrates as a HubSpot custom property. If the WayMore contact has no email, it still migrates; HubSpot accepts contacts without email addresses.

WayMore Company records map directly to HubSpot Company records. Name, domain, phone, industry, employee count, and annual revenue transfer to the corresponding HubSpot Company properties. Custom properties on the WayMore Company migrate as HubSpot custom properties on the Company object. The WayMore company domain field maps to HubSpot's domain property, which HubSpot uses to suggest company associations for contacts automatically.

WayMore Deals map to HubSpot Deals with the deal name, amount, stage, owner, and close date transferred to the corresponding HubSpot properties. The WayMore deal stage name maps to the HubSpot deal pipeline stage via value mapping. If the WayMore deal has a primary contact associated, that association migrates as a HubSpot deal-contact association after both records exist in HubSpot.

WayMore's pipeline object — the named container for deal stages — becomes a HubSpot Deal Pipeline. Each WayMore pipeline creates a separate HubSpot pipeline with its own name and stage sequence. HubSpot allows multiple pipelines; the pipeline name and order of stages are preserved exactly. If WayMore has one pipeline, one HubSpot pipeline is created. If WayMore has multiple pipelines, each gets its own HubSpot pipeline object.

WayMore deal stage names map to HubSpot deal stage names via a value-by-value lookup table. The mapping is defined per pipeline. If a WayMore stage name does not match an existing HubSpot stage, FlitStack creates a new stage in the target pipeline. Stage order is preserved. Probability percentages are not transferred from WayMore — HubSpot applies its default probability per stage or your admin sets them after migration.

WayMore custom properties on contacts (beyond the standard set) become HubSpot custom contact properties. The HubSpot property is created with the matching data type: text properties become HubSpot text, number properties become HubSpot number, pick-lists become HubSpot select. Active, archived, and hidden flags in WayMore determine whether the property is created as active in HubSpot. Custom property labels are preserved verbatim.

WayMore custom properties on companies transfer as HubSpot custom company properties, created in HubSpot before the data load. If the WayMore property is a date field, the HubSpot property is created as a date type. If it is a pick-list, the HubSpot property is created as a select type with the exact option values from WayMore.

WayMore custom properties on deals (beyond the standard deal fields) migrate as HubSpot custom deal properties. Each property is created in HubSpot with the equivalent data type. Data type conversion is applied for fields where WayMore uses a different type label than HubSpot — for example, if WayMore stores a numeric property as a text field, FlitStack converts it to a HubSpot number property on ingest.

WayMore engagement history — emails logged against contacts, call records, meeting records, and notes — migrates as HubSpot engagements on the contact timeline. Each activity becomes a separate HubSpot engagement record with the original timestamp, owner (resolved by email match to HubSpot users), and a description or subject copied from WayMore. Engagement associations to the contact are preserved.

WayMore automations and email sequences built in the visual workflow builder do not migrate. The automation logic lives in WayMore's proprietary engine and has no portable format. FlitStack exports the automation definitions (triggers, steps, conditions) as a JSON reference document that your HubSpot admin can use when rebuilding workflows in HubSpot's Workflows tool or a third-party automation platform.

Files and attachments stored in WayMore are downloaded and re-uploaded to HubSpot's file manager, associated with the relevant contact, company, or deal record. File size limits apply per HubSpot's file storage constraints. Inline images in notes are downloaded and re-hosted as HubSpot files. The original filename is preserved.

WayMore custom objects migrate to HubSpot custom objects if your HubSpot subscription is Enterprise or the Custom Objects beta is enabled. Each WayMore custom object becomes a HubSpot custom object with its own name and property set. If HubSpot Enterprise is not available, custom object records are stored as contacts with a custom property flag to indicate the original object type. Custom object associations that are N:N in WayMore need a HubSpot association object created.