Migrate your Vorex data

Tickets are the primary service desk object in Vorex. We export via the /tickets endpoint with full field coverage including status, priority, assigned technician, requester contact, and timestamps. The V2 API returns tickets as structured JSON with no schema variation between tenants.

Project dates are a known issue in Vorex — multiple user reviews document project management date fields not working properly, and QuickBooks sync problems further corrupt project financials. We re-profile all date fields before mapping and flag any records with inconsistent start/end date logic for manual review.

Time Entries export cleanly via the V2 API with billable/non-billable flags, labor rates, owner assignment, and associated project/ticket references. We preserve the billing rate and multiplier as separate fields for accurate reconstruction in the destination PSA or billing system.

Expense records export with expense type, amount, date, receipt attachment reference, and owner. We map the expense category to a destination custom field and flag any entries linked to inactive employees or vendors.

Invoices carry line items, tax codes, and QuickBooks sync flags that vary by tenant configuration. We export invoice headers and line items but note that QB sync metadata may not map directly to all destination systems. Custom invoice templates and branding are not exportable.

Client records export as the primary contact entity with name, email, phone, address, and account manager assignment. We map this directly to the destination CRM's Contact or Account object depending on the target schema.

Company (account) records in Vorex store business name, industry, size, and primary contact link. We export these alongside or merged with Clients depending on the customer's deduplication preference during scoping.

Vorex supports custom fields on tickets, projects, and clients but the V2 API exposes them inconsistently — some tenants show custom fields as flat key-value pairs, others nest them under a custom_properties object. We detect the schema variant at extraction time and map accordingly.

User and technician records export with role, email, active/inactive status, and team assignment. We map Vorex users to destination platform users, flagging any inactive records the customer did not explicitly include in scope.

Ticket and project attachments are referenced by URL in the V2 API rather than streamed directly. We extract attachment URLs and re-fetch them if the destination supports file migration, or log them as references for manual re-upload if not.