Migrate from Xpressdocs to HubSpot

Xpressdocs contact records map directly to HubSpot contacts. We preserve firstname, lastname, email, phone, and address fields as HubSpot native contact properties. Contacts without a primary company are attached to a default placeholder company or flagged for your team to assign in HubSpot after migration.

Xpressdocs stores company name as a flat contact property rather than a separate object. We extract unique company names from Xpressdocs contacts and create HubSpot company records, then link each contact to its primary company via Contact.CompanyId. Multi-contact companies collapse to a single HubSpot company record.

Xpressdocs lists are flat groupings of contact IDs. We migrate each Xpressdocs list as both a HubSpot static list (for immediate segmentation use) and a contact property capturing list membership as a multi-checkbox or pipe-delimited text field, ensuring the association survives even if static lists are deleted.

Xpressdocs real estate and listing data follows a structured JSON schema with fields like property address, listing status, MLS number, and agent details. This schema has no direct HubSpot equivalent. We create a HubSpot custom object (e.g., Property_Listing__c) matching the Xpressdocs listing schema and import all records, with a foreign key linking listings to the corresponding agent contact in HubSpot.

Xpressdocs orders contain product type, quantity, print specifications, and fulfillment status. We map completed orders to HubSpot deals with deal name, amount, and a custom property capturing order details. Since Xpressdocs has no pipeline stages, all migrated orders land in a single 'Completed' stage — your team defines pipeline stages in HubSpot to model your post-migration sales process.

Owner assignment in Xpressdocs contacts maps to HubSpot contact OwnerId. We resolve by email match against HubSpot users. Unmatched owners are flagged in the migration report — your team either creates HubSpot users for them or assigns their records to a fallback owner before the full run commits.

Xpressdocs photo assets are retrieved via the Photo Services API and re-uploaded to HubSpot's file manager. We preserve original filenames and folder structure. Images are then available for use in HubSpot email templates, documents, and workflow actions. File size limit is 256MB per asset in HubSpot.

Xpressdocs storefront configurations (brand colors, logo, approved templates) have no HubSpot CRM equivalent — these are platform-specific settings that cannot migrate. We capture the configuration as a structured JSON export for reference so your HubSpot admin can manually re-apply branding in HubSpot's design settings.

Xpressdocs APM triggers direct mail campaigns based on CRM data passing into the platform. This logic has no HubSpot equivalent at the CRM level — HubSpot's workflow engine handles the automation layer but your team must design the trigger conditions and mail-action steps. We export the APM configuration as a rebuild reference document.

Xpressdocs lead nurturing sends pre-scheduled direct mail based on enrollment lists. HubSpot sequences automate email outreach, not direct mail. The enrollment list contacts can migrate to HubSpot, and your team can build an equivalent email sequence in HubSpot Sales Hub. Direct mail automation requires a third-party integration such as Lob.

Xpressdocs order status values (Pending, Processing, Shipped, Delivered) map to a custom pick-list field on the corresponding HubSpot deal. Each status is mapped to a pick-list option, and we preserve the original timestamp as a custom datetime field for audit continuity.

Xpressdocs print templates are proprietary file formats tied to the Xpressdocs print production engine. They cannot migrate to HubSpot. We recommend downloading your active template set from Xpressdocs before account closure and managing print collateral through HubSpot's document template feature or a connected print-on-demand integration like Lob.