Migrate from Altcraft to HubSpot

Altcraft profiles migrate as HubSpot contacts. Profile attributes with scalar values map directly to HubSpot contact properties. Profiles with multiple company associations collapse to a primary company; secondary companies use HubSpot's Company Contact Associations feature. Each contact retains the original Altcraft profile ID in a custom property for traceability and subsequent delta imports.

Altcraft company records map 1:1 to HubSpot company records. Company domain, address, and engagement fields map to HubSpot company properties. Parent-child company hierarchies use HubSpot's Parent Company field for the top-level link. If a company lacks a parent, the top-level record remains as a standalone HubSpot organization with no parent link.

Altcraft campaigns carry engagement summary data (total_sent, delivered, opened, clicked) and budget. These aggregate metrics migrate as custom properties on a HubSpot deal record named after the campaign. Deal stage is set to the mapped Altcraft status value. The campaign budget maps to the deal amount, preserving historical financial context for reporting.

Altcraft campaign status values (planned, active, completed, archived) map to HubSpot deal stage pick-list values. The mapping plan is delivered before migration runs so HubSpot admins can create any missing stage values. If custom statuses exist, we add them to the pick-list and document the mapping for audit.

Altcraft scenarios are event-triggered, branching automation sequences with conditions and multiple action types. HubSpot workflows are enrollment-triggered. FlitStack exports scenario definitions as a structured JSON reference document that maps triggers, conditions, and actions to HubSpot workflow concepts. Teams use this reference to rebuild each scenario in HubSpot's workflow builder.

Altcraft stores per-channel subscription flags (email, SMS, push, messenger) as profile attributes. HubSpot has no native multi-channel preference object. We create one HubSpot contact property per unique channel flag found in your Altcraft profiles and preserve the boolean value. These custom properties enable reporting on channel opt-in status.

Per-profile engagement counts (emails_sent, emails_opened, clicks, SMS_sent) from Altcraft aggregate as custom number fields on the HubSpot contact. Campaign-level aggregates migrate as custom number fields on the related deal. Historical counts are preserved for trend analysis and segmentation in HubSpot reporting tools.

Altcraft custom profile fields map to HubSpot custom contact properties. Field data type (string, number, date, boolean) is inferred from Altcraft values and applied to the HubSpot property. Fields with mixed data types are flagged for admin review before migration.

Altcraft profile tags migrate as HubSpot contact properties. If the tag set resembles personas, we map to HubSpot's built-in Persona property; otherwise, we create a custom comma-separated text property or multiple boolean properties based on tag cardinality. This approach preserves tag semantics and simplifies segmentation in HubSpot.

Altcraft segments are named collections of profiles based on property conditions. We recreate Altcraft segments as HubSpot static lists and, where possible, as HubSpot smart lists using the equivalent filter logic. Dynamic rules are documented as a rebuild reference. This documentation helps your team replicate complex segment logic in HubSpot's list builder.

Altcraft product and order data migrates as HubSpot line items linked to the deal, with product name, SKU, quantity, and price as line item properties. Complex order histories require a custom object to preserve full order context. Custom objects store order identifiers, timestamps, and fulfillment status for comprehensive audit trails.

Altcraft profile activity events (email sent, email opened, SMS received, push notification clicked) migrate as HubSpot engagement records on the contact timeline with original timestamps and event type preserved. These records enable detailed activity reporting and help maintain historical interaction data in HubSpot.