Migrate your SYDLE ONE data

SYDLE ONE's core BPM engine stores Process definitions with BPMN notation, forms, and execution history. We export Process definitions as structured JSON and preserve historical execution records as a separate dataset for destination mapping.

ECM stores files and content records with metadata including owner, date, and associated entities. Documents can be exported in bulk and re-associated to target objects using metadata tags captured during the export phase.

The CRM core manages Contact records with standard fields (name, email, phone, lifecycle stage) and supports custom properties. We migrate Contacts 1:1 and flag any custom field names that require schema creation at the destination.

Account/Company records are linked to Contacts and Opportunities. We preserve the Account-Contact relationship at migration time and remap Account IDs to destination values post-transfer.

Service Desk tickets support custom fields and status workflows. Ticket statuses vary by configuration, so we map the source status values to destination pipeline stages explicitly rather than relying on default ordering.

Deal records include stage, value, owner, and close date. Pipeline stage values differ across implementations, so we build an explicit stage-mapping table before executing the import.

HR Recruitment is a SYBOX module available on Planet and Star tiers. Candidate records, job openings, and application statuses migrate with field-level mapping to the destination ATS or HR system.

Agile Project Management is a SYBOX add-on. Projects, sprints, and task records migrate, but sprint velocity and burndown history require a separate export sequence to preserve historical data integrity.

Service Portal records and portal page configurations are exported as JSON structures. Because portal routing rules reference ticket and contact IDs, we remap those IDs during the import sequence to maintain portal functionality.

Chatbot flows built for WhatsApp, Facebook, Telegram and other channels are stored as process-like objects. We export the flow logic and re-import via the platform's configuration import mechanism.

Billing is a Planet/Star module covering contracts, orders, and payment records. Because billing objects reference Accounts and Contacts, migration sequencing places billing after CRM objects to preserve referential integrity.

Dashboards and KPI indicators reference specific object fields and records. We export the dashboard definition separately from the underlying data, and flag any metric that depends on migrated records for reconfiguration at the destination.

SYDLE ONE supports custom objects but the exact field schema is implementation-specific. We read the target instance's custom object definitions via the admin interface before building the field map for any non-standard objects.

File attachments on any record type migrate as standalone files with a reference back to their parent object. We preserve the attachment association by writing a mapping table alongside the file export.

Tags applied to Contacts, Accounts, Tickets, and Processes migrate as label sets. We normalize tag names that contain special characters before importing to avoid validation errors.