Migrate from XMPie to Nutshell

XMPie recipient lists are the primary contact repository — each recipient row maps directly to a Nutshell Person record. First name, last name, and email are mapped field-for-field. Phone, address, and custom fields migrate as Nutshell standard or custom fields on the Person record. Nutshell's Person API entity type is returned as 'Contacts' in the JSON-RPC response.

Email is the primary unique identifier for matching recipient records in XMPie to Nutshell People. If a recipient lacks an email, FlitStack AI attempts matching on first name + last name combination and flags records requiring manual review in Nutshell before the migration commits.

XMPie Audience segments define subgroups within a recipient list. These map to a custom picklist field on Nutshell Person (e.g., Segment_Affinity__c) because Nutshell has no native segment or tagging concept for People beyond notes. Nested segments use pipe-delimited values in the custom field.

XMPie campaigns represent cross-media production runs (print + email + web). Nutshell has no campaign production object — campaign metadata is preserved as a custom text field on the Person record and as Activity entries with campaign name in the subject line. Actual campaign assets (personalized PDFs, email HTML) do not migrate.

When XMPie uStore generates orders (product purchases triggered by campaign links), those order records map to Nutshell Deals. The Deal name uses the uStore order number, amount maps from the order total, and close date maps from the order completion timestamp. Each order-line item becomes a custom field on the Deal.

XMPie recipients can have an associated company field. This maps directly to a Nutshell Company record. FlitStack AI creates the Company record first, then links the Person record via the Person-Company association map. If no company is listed, the Person attaches to a default 'Unassigned Company' record.

uStore product definitions include name, SKU, pricing tiers, and customizable options. Nutshell has no native product catalog — product names and SKUs migrate as custom fields on the associated Deal. For complex product configurations with multiple options, a custom object (Product_Config__c) is created in Nutshell and linked via a lookup.

XMPie personalization fields beyond name/email/phone (e.g., loyalty tier, birthday, product preference) become Nutshell custom fields on Person. Field type is inferred from XMPie content object type: text content objects map to text fields, numeric content objects map to number or currency fields, date content objects map to date fields.

XMPie tracks email engagement events (send, open, click). Nutshell has activity logging but no equivalent native engagement tracking for campaign emails. Engagement history is preserved as Activity records with campaign name and event type in the subject, with original timestamps. Marketing engagement metrics require Nutshell's Engagement add-on post-migration.

XMPie production logs record print job status, output format, and fulfillment details. Nutshell has no print fulfillment object. Summary print output information is stored as a Note on the associated Person record. Actual PDF or print files are not migrated — they remain in XMPie's document repository.

XMPie users with access to campaigns are matched to Nutshell Users by email address. Unmatched users are flagged before migration — your Nutshell admin either invites them to the workspace or assigns records to a fallback owner. XMPie role permissions (Power user vs standard) do not map to Nutshell roles.

XMPie recipient lists can pull from external SQL databases or Excel uploads. External data sources are not migrated — only the snapshot of data attached to the recipient list at migration time moves to Nutshell. Your team should re-establish the data connection in your operational systems post-migration.