Migrate from Xpressdocs to Freshsales

Xpressdocs Contact Lists map directly to Freshsales Contact records. Each contact's email address, name, phone, and address fields map to Freshsales standard Contact fields. List membership is preserved as a Freshsales contact segmentation field or tag. We extract contact records via the Xpressdocs CRM API endpoint with pagination and batch sequencing, then ingest via Freshsales Contacts API.

Xpressdocs Storefronts (top-level brand containers with product catalogs and user permissions) map to Freshsales Account records with custom fields for storefront-specific metadata. Storefront-level settings like branding configuration and template library are not directly migratable; we preserve the metadata reference and note which settings require manual reconfiguration in Freshsales.

Xpressdocs print products (postcards, brochures, door hangers, business cards) map to Freshsales custom product records or Deal line items depending on whether the customer uses Freshsales Products. Product definitions including paper type, coating, and pricing are preserved in custom fields on the product record. We map the Xpressdocs product reference ID for reconciliation.

Xpressdocs Order history maps to Freshsales Deal records. Order fulfillment status, delivery method, and quantity migrate to Deal fields. Line-item product references map to custom fields or Deal Products. We use the Order's creation timestamp as the Deal creation date and preserve order ID as an external reference field for audit trails.

Xpressdocs Storefront users (Admin, Designer, Orderer roles) map to Freshsales User records. We resolve by email match and preserve role designation as a custom field on the User record since Freshsales role architecture differs from Xpressdocs permission model. Users without a matching Freshsales User are flagged for manual provisioning before record import.

Xpressdocs marketing templates are brand-approved print designs stored per-storefront with variable-data placeholder fields. We export template metadata and field definitions but flag them as requiring Freshsales document management or a separate DAM tool for storage, since Freshsales does not have a native template management module. Template placeholder field definitions are preserved in a custom field for reference during rebuild.

The Xpressdocs JSON Listing Feed (Agent, Property, Open House, Buyer/Seller, Picture objects) has no Freshsales native equivalent. We design a Freshsales Custom Object named Property with fields for address, listing status, price, agent association, and open house dates. Agent and Buyer/Seller records map to Contact records with a custom object link. MLS re-integration requires a separate setup step post-migration.

AmazingMail automated direct mail triggers are event-driven rules tied to CRM events like service reminders, birthdays, or appointment completions. These triggers are not directly migratable because they reference Xpressdocs-specific event hooks. We document each trigger definition (rule conditions, contact segment, mailer type, timing) as a written specification for the customer to rebuild in Freshsales Workflows or a third-party automation tool post-migration.