Migrate from YetiForce CRM to HubSpot

YetiForce Companies map 1:1 to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue transfer as HubSpot default properties. Parent-child company hierarchies in YetiForce map to HubSpot's parent company field. Multi-company associations that YetiForce supports require HubSpot to use a primary company with additional associations stored as custom properties.

YetiForce Contacts map directly to HubSpot Contacts. First name, last name, email, phone, mobile phone, job title, and address fields transfer as HubSpot default properties. The owner's email resolves to a HubSpot user ID for assignment. Original YetiForce create dates preserve as a custom datetime property since HubSpot sets CreatedDate at import time.

YetiForce Leads split by lifecycle intent. Leads with active engagement history and sales touchpoints become HubSpot Contacts with a custom lifecycle-stage property set to reflect YetiForce lead status. Cold, unqualified leads that have received no outreach become HubSpot Leads, which the sales team qualifies and converts manually post-migration. The split rule is configurable per migration plan.

YetiForce Potentials map to HubSpot Deals. Deal name, amount, close date, and owner transfer directly. YetiForce pipeline and stage names map value-by-value to HubSpot pipeline stage names. Pipeline-to-pipeline mapping is configured per the client's HubSpot pipeline count. HubSpot Sales Hub Starter includes one pipeline; additional pipelines require Sales Pro or Enterprise.

YetiForce Product Catalogue items map to HubSpot Products. Product name, unit price, cost price, vendor, and description fields transfer as HubSpot product properties. YetiForce product images and attachments re-upload to HubSpot's file manager and link to the product record. Products must exist in HubSpot before they can be associated with Deals, so product migration runs before or concurrent with Deal migration to preserve line item associations.

YetiForce Trouble Tickets have no direct HubSpot equivalent in the Sales CRM alone. If the client has HubSpot Service Hub, tickets migrate as native HubSpot Tickets linked to Contacts and Companies. Without Service Hub, tickets migrate as a custom Ticket object or custom properties on the related Contact/Company. Ticket status, priority, category, and resolution notes map to custom fields.

YetiForce Projects span multiple CRM and PM use cases. Project records that represent pre-sale opportunities map to HubSpot Deals with a project-type custom property. Operational projects with deliverables and milestones map to a HubSpot custom object created by the admin before migration. Project-task sub-records require either a custom sub-object or an attachment with the task list exported as a formatted file.

YetiForce Call List and Email List entries map to HubSpot Tasks with Task Type set to 'Call' or 'Email'. Original call duration, outcome, and timestamp transfer as custom properties on the Task. Activities are attached to the parent Contact or Company record by YetiForce's record ID preserved on the HubSpot task for traceability. Email subject lines and body text transfer to the Task description field for complete activity context.

YetiForce Calendar meetings map to HubSpot Meetings (Events) with original start and end times, location, and description preserved. Meeting attendees link to HubSpot Contact records by email. YetiForce recurring meeting series are flattened into individual meeting records, with a custom property flagging the recurrence pattern for manual rebuilding in HubSpot's meeting scheduling tools.

YetiForce document attachments on records re-upload to HubSpot Files. File size limits apply (HubSpot default 25MB per file, with batch upload support for larger datasets). Inline images embedded in YetiForce notes are extracted, downloaded as image files, and re-uploaded to HubSpot before note text is migrated, ensuring images display correctly in the destination system.

YetiForce allows any record to link to any other record type via a flexible Related To relationship. HubSpot's association model is fixed per object type. We store the full set of YetiForce relationship IDs as a custom text property on each record, enabling your admin to rebuild the associations manually in HubSpot using a reference list.