Migrate from Xpressdocs to Pipedrive

Xpressdocs Contact Lists drive direct mail campaigns and AmazingMail triggers. We extract each contact record preserving list membership as a custom multi-select picklist field or Pipedrive Label. Email addresses, phone numbers, names, and physical addresses map to Pipedrive's standard People fields. Any segmentation tags or contact sources (e.g., lead source, acquisition channel) are preserved as custom fields. Merge rules and duplicate handling are documented separately for the customer admin to resolve before import.

Xpressdocs contacts may belong to an organization (e.g., franchisee, real estate brokerage, insurance agency). Where a company name or organization field exists on the contact record, we extract it as a separate Organization record and link the People to it via the OrganizationId field. This step requires a pre-migration decision on whether to flatten contacts as standalone People or build the Organization hierarchy based on Xpressdocs list structure.

Xpressdocs Products (postcards, brochures, door hangers, business cards) with paper type, coating, and pricing migrate to Pipedrive Products with Product2 records and Standard Price Book entries. Print-specific attributes like paper weight, finish, and template ID are preserved as custom fields on the Product record. Note that Pipedrive Products are primarily designed for deal-line-item quoting; they do not capture print production specs, so we document the full product attribute set before import so the customer admin can decide which specs to retain.

Xpressdocs Order history (fulfillment status, delivery method, quantity, line-item product references, recipient contacts) does not have a direct Pipedrive equivalent. We preserve Order data as Note records linked to the associated People record, with a custom field set capturing order_id, product_name, quantity, fulfillment_status, and order_date. This gives sales reps visibility into historical print activity without distorting Pipedrive's activity or deal model. Customers with heavy order histories may choose to exclude closed orders from the migration and reference them in a separate report.

Xpressdocs Storefronts are top-level brand containers containing product catalogs, template libraries, and user permissions. Pipedrive does not have a native Storefront equivalent. We map each Storefront to an Organization record with the storefront name and brand configuration captured as custom fields. User roles per storefront (Admin, Designer, Orderer) are mapped to Pipedrive Users with a custom role field if the customer has multiple storefronts and needs role differentiation across brands.

Xpressdocs Users and their role assignments (Admin, Designer, Orderer) export by email and name. We resolve each Xpressdocs user to a Pipedrive User record by email match. Role naming conventions differ between Xpressdocs tiers and Pipedrive's standard user model, so we map roles by permission level rather than by name. Any Xpressdocs user without a matching Pipedrive account is held in a reconciliation queue for the customer's admin to provision before record import.

The Xpressdocs JSON Listing Feed maintains Agent, Property, Open House, Buyer/Seller, and Picture objects that are not part of the standard Xpressdocs CRM export. We export the listing feed schema separately and map agent records to People, property listings to custom fields on the agent's Organization record, and open house details to custom fields or Notes. This requires a custom field architecture review with the customer because Pipedrive's native schema does not accommodate the full real estate data model without significant customization.

Xpressdocs marketing templates are brand-approved designs stored per-storefront with variable-data placeholder fields. Custom templates with variable-data fields are exported with template_id, name, and placeholder field definitions preserved as a Note linked to the associated Organization. The actual template asset files (PDF, design files) do not migrate through the API; we document the template inventory and flag file transfer separately.

Brand-specific image galleries in Xpressdocs store logos, brand colors, and approved photography as platform assets. The asset metadata and URL references export separately; the image binaries themselves are not exposed through the standard API. We preserve URL references and gallery metadata as Notes or custom fields on the Organization record, with a separate file transfer recommendation for the actual image assets.

AmazingMail direct mail triggers are rule-based campaigns tied to external CRM events (service reminders, birthdays, appointment completions). Trigger logic is not automatically portable across platforms because the event hooks reference external systems. We export each trigger definition (conditions, contact segment, mailer type, and timing) and deliver a written inventory recommending equivalent Pipedrive Automation rules or Power Automate flows. Re-implementation is a manual step for the customer's admin.