Migrate from XMPie to HubSpot

XMPie exports recipient records containing first name, last name, email address, phone, and custom personalization fields. Each recipient becomes a HubSpot contact. The email address serves as the primary deduplication key during load. If a contact with the same email already exists in HubSpot, we update the existing record rather than creating a duplicate, preserving any pre-existing data you may have.

XMPie stores company as a free-text field on the recipient record. We create or match a HubSpot company record using the company name, then associate the contact via the primary company link. Multiple recipients sharing the same company name collapse to a single company record.

XMPie Circle audiences contain named segments with rule-based filtering. Each segment is translated to a HubSpot static list (if the source is a snapshot export) or an active list with equivalent dynamic criteria (if the source segment rules can be expressed in HubSpot's filter logic). Segment priority ordering is preserved as a custom property for reference.

XMPie campaign names and campaign IDs are stored as custom contact properties (e.g., campaign_source__c) so you can filter contacts by the originating XMPie campaign. Full campaign history linking is preserved as a text audit trail since HubSpot has no native campaign-object equivalent for outbound communications.

uStore exports include product name, catalog number, external ID, and description. These map directly to HubSpot product records. Kit products (bundles) from uStore become HubSpot products with associated line items representing the kit components. The catalog number maps to the HubSpot SKU field, and the external ID is preserved in a custom property for reconciliation against your uStore product database.

XMPie uStore order records contain buyer contact, product purchased, quantity, price, and order status. We map each order to a HubSpot deal (representing the transaction) with line items representing the products purchased. The order total maps to the deal amount.

XMPie template variables—custom fields defined per audience or campaign—become HubSpot custom contact properties. We create the property in HubSpot, assign the appropriate data type (text, number, date, picklist), and preserve the original XMPie field label in the property description for traceability.

XMPie InDesign-linked document templates (uCreate Print) contain personalization rules, content objects, and design assets. These do not have a migration path to HubSpot. We provide a template audit listing all variable names and rules so your design team can recreate personalization logic in HubSpot tokens or workflow enrollment criteria.

XMPie tracks print job runs, production timestamps, and output logs. HubSpot has no native print production log. These records are not migrated; we document the last job run date per audience as a custom contact property for audit purposes if needed.

XMPie recipient address fields (street, city, state/province, postal code, country) map to HubSpot's standard address properties on the contact record. Multi-line street addresses are preserved as a single text string in HubSpot's address1 field. If XMPie stores address components in separate fields that do not align with HubSpot's standard address schema, we concatenate them into the appropriate HubSpot address properties during the transformation step.

XMPie email campaign send/open/click data is available via Circle reporting exports. We map send records to HubSpot contact properties (last email sent date) and create engagement timeline entries for opens and clicks using HubSpot's engagement API so the activity appears in the contact timeline.

XMPie Circle users are identified by email. We match XMPie users to HubSpot users by email address. If a HubSpot user account does not exist for an XMPie user, the contact's owner is set to a designated fallback user and flagged in the migration report for manual reassignment.