Migrate from Neoforce to HubSpot Service Hub

Neoforce Tickets map to HubSpot Tickets with full custom-field payload preserved. We map Ticket status (open, pending, resolved, closed) to HubSpot pipeline stages, priority to the ticket priority property, category to a custom ticket property, and assignee to the HubSpot owner. Custom field types (string, number, date, boolean, picklist) map to their HubSpot equivalents. Conversations and comments on tickets migrate as Ticket conversations with author attribution and timestamp preserved.

Neoforce Company records map directly to HubSpot Companies. Company name, address fields, domain, and all custom properties migrate as typed HubSpot company properties. The HubSpot Company record is created before any Contact or Ticket import so that the association relationship is satisfied at the moment of insert. Companies without a HubSpot equivalent (e.g., one-off organisations with no CRM value) are flagged for the customer's admin to merge or archive post-migration.

Neoforce distinguishes between full Agent accounts and free Light Accounts used by portal end customers. Light Accounts may lack an email address or full contact details in some export scenarios, which creates a reconciliation challenge: HubSpot Contacts require an email address as the primary identifier. We flag all Light Account records during scoping, apply a configurable email-placeholder strategy (e.g., placeholder-{id}@placeholder.local) for incomplete records, and surface them in a reconciliation report so the customer can enrich or suppress them before go-live. Where a Light Account does have a valid email, it maps directly to a HubSpot Contact.

Neoforce Agent accounts (full users) map to HubSpot Users by email match. Role names and permission levels from Neoforce are preserved as custom properties on the HubSpot User record (e.g., neoforce_role__c, neoforce_permissions__c) so the customer's HubSpot admin can reconfigure roles post-migration without losing the source-of-truth permission structure. Inactive Neoforce agents map to inactive HubSpot Users.

Neoforce's asset management module has no direct HubSpot Service Hub equivalent. On Professional tier, asset records require either mapping to a HubSpot Custom Object (Enterprise tier only) or attaching asset metadata to the related Company record as custom fields. We advise during scoping whether the customer needs HubSpot Enterprise for a dedicated asset Custom Object, or whether asset records can attach to the related Company as structured custom fields. In either case, we preserve asset ID, name, type, status, serial number, and linked contract reference.

Neoforce Contract records (linked to Assets and Companies, storing terms, renewal dates, and custom fields) require a destination schema decision. HubSpot Service Hub has no native contract object. On Enterprise tier, we create a Contracts Custom Object with renewal date, contract type, and linked Company as custom properties. On lower tiers, we attach contract metadata to the related Company record. Renewal date semantics and contract-type categorisations vary between Neoforce and HubSpot, so we document the source vocabulary for the customer's admin to normalise post-migration.

Neoforce SLA definitions (response time targets, resolution time targets, escalation thresholds, and escalation chain rules) are stored as configuration objects rather than ticket attributes. They do not transfer programmatically. We export the full SLA tier matrix — response targets, resolution targets, escalation timings, and which agent groups receive escalations — and document it in the migration workbook. The customer's HubSpot admin configures matching SLA Policies in HubSpot Service Hub using the FlitStack AI SLA documentation as the source-of-truth configuration blueprint.

Neoforce wiki article content and metadata (title, body, folder structure, article status) migrate as HubSpot Knowledge Base article drafts. We extract the article content and category hierarchy from the Neoforce export and structure it as HubSpot article JSON, preserving author attribution where available. Images embedded in articles are flagged for re-upload to HubSpot's file manager since attachment references are destination-specific. The customer reviews and publishes each article in HubSpot's Knowledge Base editor, with FlitStack AI delivering a complete content package per article ready for paste-and-publish.

Tags applied to Tickets, Assets, and Companies in Neoforce are exported as a flat tag array per record. We migrate the tag vocabulary to HubSpot Tags and apply the tag array to the corresponding Tickets and Companies in HubSpot. Tag-based segmentation in HubSpot works identically to Neoforce for filtering and reporting purposes.

Neoforce custom fields on Tickets (string, number, date, boolean, picklist, multi-select) map to HubSpot custom properties on the Ticket object. We export the full custom field schema — name, data type, required flag, and picklist options — alongside the field values so the destination receives both the structure definition and the populated data. Picklist options from Neoforce migrate as HubSpot option label mappings, with any Neoforce-specific terminology noted for the customer's admin to relabel in HubSpot.

Ticket attachment binary references from Neoforce are preserved as file references mapped to HubSpot's file storage. We migrate attachment file names, MIME types, and the original upload timestamps. Inline images in ticket comments migrate as HubSpot-hosted files with the inline image URL updated in the comment body to point to the HubSpot file URL. Very large attachment files (exceeding HubSpot's file size limits) are flagged for the customer to store externally and link via custom property.

Neoforce workflow definitions (triggers, conditions, branching logic, downstream actions) are stored in a proprietary format not accessible via the public API. There is no bulk-export endpoint for automation rules. We cannot migrate workflows as executable code. We run a discovery sprint that produces a Workflow Inventory Document listing every active Neoforce workflow with its trigger, conditions, actions, and a recommended HubSpot Service Hub Workflow equivalent. The customer's admin rebuilds each workflow in HubSpot using the FlitStack AI inventory as the configuration blueprint.