Migrate from Xpressdocs to Nutshell

Xpressdocs contact lists are flat groupings of contacts used for direct-mail campaigns. We export each contact list separately and map contacts into Nutshell People records, preserving list membership as Tags on each Person record. If the customer uses list names as a primary segmentation dimension, we create Nutshell Tags (e.g., Tag: storefront-name-listname) to replicate the segmentation logic. Multi-list contacts are de-duplicated by email address and cross-referenced to avoid creating duplicate People records.

Individual contact records migrate to Nutshell Person with name fields, email address, phone, physical mailing address (critical for direct-mail campaign recipients), and any custom contact properties mapped to Nutshell custom fields on Person. The Nutshell Person is created before any associated Company record to satisfy the lookup relationship. We flag contacts without email addresses for the customer to resolve manually, since Nutshell requires an email for CRM-level contact records.

Xpressdocs Storefronts are brand containers tied to specific locations or agents. We map storefronts to Nutshell Company records, using the storefront name as the Company name and the primary contact from that storefront as the linked Person. This preserves the storefront-to-contact relationship in the CRM model. If a storefront has multiple contacts, we link the primary contact to the Company and attach the remaining contacts as related People with a Tag identifying their storefront.

Xpressdocs print products (postcards, brochures, door hangers, business cards) with paper type, coating, and pricing do not have a direct Nutshell equivalent since Nutshell has no native product catalog object in its CRM tier. We map product data to custom fields on Nutshell Deal records or to a Nutshell Product configuration (if the customer uses Nutshell's built-in Product feature). Product definitions are preserved as a reference table delivered alongside the migration for the customer's admin to configure post-import.

Xpressdocs order history with fulfillment status, delivery method, line items, and contact recipients migrates to Nutshell as Activity records (Notes or Tasks) attached to the relevant Person or Deal. Each order generates a Note with the order number, date, products ordered, quantity, and fulfillment status. If the order is tied to a Deal in Nutshell, we link the Activity to that Deal for pipeline reporting context.

Xpressdocs storefront users and their role assignments (Admin, Designer, Orderer) map to Nutshell Users by email match. Role naming conventions differ between platforms, so we map by permission level rather than by name: Xpressdocs Admin maps to a Nutshell admin User, Designer maps to a standard Nutshell User with appropriate record access, and Orderer maps to a Nutshell User with read and write access to People and Deals. We flag any Xpressdocs users without email addresses for manual provisioning.

The Xpressdocs JSON Listing Feed API maintains property records with Agent, Property, Open House, Buyer/Seller, and Picture objects that are not native CRM concepts. We export listing feed data separately from contact lists and map property fields to custom fields on the Nutshell Company or Person record associated with the listing agent. Listing associations are preserved as Notes on the Person record. This data requires a custom field configuration step in Nutshell before migration.

AmazingMail direct-mail triggers are rule-based campaigns tied to CRM events (service reminders, birthdays, appointment completions) configured against an external CRM. We document each trigger definition (trigger event, contact segment, mailer type, cadence) in a written inventory delivered alongside the migration. These rules do not migrate as automation — Nutshell's CRM layer does not include marketing automation. The customer's admin rebuilds triggers in Nutshell's activity follow-up model or a connected marketing automation tool.

Marketing templates (brand-approved postcard, brochure, and door-hanger designs stored per-storefront) are Xpressdocs platform assets, not structured database records. We document the template library per storefront, including template name, variable-data placeholder fields, and the associated product type. Actual template files are not exportable through the API. The customer downloads template assets directly from Xpressdocs for re-upload to their new print fulfillment vendor.

Brand-specific image galleries in Xpressdocs are stored as platform assets, not structured database records. We export the asset metadata and URL references in a written handoff document. Image files must be transferred separately via direct download from Xpressdocs or requested from Xpressdocs support, since the image binaries are not exposed through the standard export endpoints.