Migrate your XMPie data

Audience is the top-level container for recipient data in Circle. Each Audience contains one or more Segments defined by parameter rules. We preserve the full audience hierarchy and segment definitions, including color-coding and precedence order, during migration.

Segments are defined by parameter-based rules within an Audience. They have a defined precedence order where higher segments take priority. We capture segment logic and the ordered list, re-creating the rule tree in the destination system.

Campaigns in Circle are the orchestration layer containing multiple Touchpoints across print, email, SMS, and web channels. We preserve the campaign structure, its associated touchpoint list, and scheduling/automation settings.

Touchpoints represent individual communications within a Campaign such as a printed piece, email, SMS, or web page. We migrate touchpoint configuration, linked content objects, and the recipient routing from audience segments.

Products in uStore support static, kit, easy-upload, and dynamic types. Delivery settings and pricing are not exported per XMPie's documentation. We flag these as requiring manual reconfiguration post-migration. Dynamic product recipient list settings may have system-specific options that are not portable.

Content Objects in uCreate Print are linked to data source columns and define how content renders per recipient. Types include Text, Graphic, Table, Visibility, Style, Link, and Multi-Page PDF Table. We migrate the object definitions and their rule expressions, though some rule expressions may reference server-specific pathing.

Variables in uCreate Print are the named references to data source fields or computed expressions. They power content object rules and personalization logic. We preserve variable names, types, and their assigned data fields during migration.

XMPie Packages (.dpkg) bundle a dynamic document with all related resources. Document packages and XLIM packages can be exported. XLIM files (.indx) contain the document only without dependencies. We extract and transfer package contents where feasible, noting that 3D products and uEdit settings are excluded from export.

Data Sources feed recipient data into campaigns and are linked to content object creation. We migrate the connection configuration and column definitions, though the actual data files (Excel, CSV, database exports) must be reconnected at the destination server.

Stores in uStore contain the storefront design and basic settings, exportable as a package. We transfer the store package, but delivery configuration and payment integration must be rebuilt at the destination.

XMPie uses Adobe InDesign as the native design environment via the uCreate Print plugin. InDesign documents tagged with XMPie properties can be exported to IDML and INX formats. We preserve document structure and XMPie properties where the export option is enabled.

Business rules in content objects define dynamic formatting, conditional visibility, arithmetic operations, and personalization logic per recipient. We extract rule definitions, though complex rules referencing external server paths or custom Qlingo extensions may require reimplementation.