Migrate your Service Creatio data

Cases are the primary service object in Service Creatio. We migrate cases with full field fidelity including custom columns, status, priority, owner assignment, and SLA timers. Case number generation in the destination is handled per the target system's rules.

Contacts hold the customer person record. We map ContactId, name fields, email, phone, and custom Contact properties. We preserve the link between a case and its primary Contact record during migration.

Accounts store the organizational customer record. We migrate account hierarchy, address data, industry classification, and custom Account fields. Accounts load before Cases to preserve referential integrity.

KB articles are stored with title, body content, category assignment, and publication status. We preserve article-to-category structure and re-link articles used in case resolution flows at the destination.

Activities track individual interaction events tied to a case or contact. We migrate activity type, subject, due date, completion status, and the parent record reference. Recurring activity patterns are preserved as individual instances.

SLAs define response and resolution time commitments per case category. We map SLA rules to the destination's SLA configuration, noting that Creatio's SLA engine uses specific time-bound condition logic that requires manual alignment at the destination.

Queues group cases for team or individual assignment. We export queue membership and routing rules, but queue-to-user assignment mappings require review because destination queue structures often differ in naming and hierarchy.

Custom objects created in Creatio Studio via the Object type schema are fully supported for extraction, but each requires explicit schema discovery. We extract the object definition and all rows, then map relationships to standard objects based on lookup column references.

Standard objects like Cases, Contacts, and Accounts can have custom fields added via the UI designer. We identify all custom fields during discovery and map them to destination custom properties, flagging any that lack a clear destination equivalent.

File attachments are stored via File-type schemas (e.g. ContactFile). Large attachment sets require careful chunking during export to avoid triggering the OData RAM limit. We extract file binary data and re-attach at the destination using the target system's file API.

Creatio Users serve as case owners, activity assignees, and queue members. We map Creatio users to destination users by email lookup. Inactive users are preserved as historical owners rather than reassigned.

Tags are label objects applied to cases and contacts. We export tag names and their associations. Destination systems that use a different tagging model (e.g. label-based vs. taxonomy-based) require value mapping at migration time.