EU, US and India data residency · a DPA you can sign
Trust Center →ServiceNow to FlowTux: move the queue, leave the CMDB
Nobody moves a whole ServiceNow instance to FlowTux, and you should not try. What moves is the front door: incidents and catalog requests. Change, problem and the CMDB stay in ServiceNow, read-only or still licensed.
Getting your data out of ServiceNow
Each line below was checked against ServiceNow’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.
- List export
- Right-click a list column header > Export. Excel, CSV, JSON and PDF are open to all users; XML needs the admin role. Source: servicenow.com
- Row limits
- Each export format defaults to 10,000 rows (glide.csv.export.limit, glide.xlsx.export.limit and so on). PDF defaults to 1,000. Source: servicenow.com
- URL export
- incident_list.do?CSV&sysparm_query=... exports a filtered list. The XML URL export leaves out attachments and journal fields. Source: servicenow.com
- Table API
- GET /api/now/table/{table} with sysparm_query, sysparm_limit and sysparm_offset. Reference fields return a sys_id unless you pass sysparm_display_value=all. Source: servicenow.com
- Journal fields
- Comments and work notes are stored in sys_journal_field. Query it by element_id (the record’s sys_id) and element (comments or work_notes). Source: servicenow.com
- Attachments
- GET /api/now/attachment lists metadata; GET /api/now/attachment/{sys_id}/file returns the file. Source: servicenow.com
- Rate limits
- Set per instance as hourly Rate Limit Rules (sys_rate_limit_rules). ServiceNow documents no default; over the limit returns HTTP 429 with Retry-After. Source: servicenow.com
- Requests
- Catalog requests span three tables: sc_request, sc_req_item and sc_task. Catalog variables live only on sc_req_item. Source: servicenow.com
- Knowledge
- GET /api/sn_km_api/knowledge/articles lists articles; /articles/{id} returns one by sys_id or KB number. Source: servicenow.com
Not verified
We could not confirm these from ServiceNow’s documentation. Check them in your own account.
- Whether CSV or Excel list exports include journal content.
- Field lists for sys_user, sys_user_group and cmdb_ci.
- The reference field names linking sc_req_item and sc_task to their parents.
Field mapping
What each ServiceNow field becomes in FlowTux. We confirm every row with you before loading.
| ServiceNow | FlowTux | Notes |
|---|---|---|
| number (INC…, RITM…) | Original ticket number, kept on the imported ticket | Incidents and request items both become tickets. |
| short_description, description | Ticket title and first message | |
| state | Status: Open, In Progress, Resolved, Closed | State choices vary by instance; map yours on the call. |
| priority, impact, urgency | Priority: Critical, High, Medium, Low | Impact and urgency are kept as context. |
| category, subcategory | Category, the starting taxonomy Tux AI triages against | |
| caller_id (sys_id) | Requester, matched by email address | Resolve sys_ids with sysparm_display_value=all, or join sys_user on email. |
| assigned_to, assignment_group | Owner: an Admin or Agent member | |
| comments (journal) | Comment on the ticket thread | |
| work_notes (journal) | Internal note, never shown to the requester | |
| close_code, close_notes | Resolution note | |
| cmdb_ci | CI name recorded on the ticket | The CMDB itself stays in ServiceNow. |
| catalog variables (sc_req_item) | Ticket body, or archive | FlowTux has no documented custom-field object. Values you need are written into the ticket during import; the rest stay in the archive. Agreed field by field on the scoping call. |
| kb_knowledge article | Knowledge base article in the Support Portal (write it, import a page by URL, or upload a file) |
What carries over
- Incidents and request items in the window you choose
- Customer-visible comments and work notes, kept apart
- Callers and assignees, resolved from sys_id to email
- Category and subcategory, as FlowTux categories
- Knowledge articles you choose to reload
What does not
- The CMDB, discovery and service mapping
- Change, problem and release records
- Flow Designer flows, business rules and client scripts
- The service catalog definitions and approval chains
- Reports, dashboards and SLA definitions; targets are restated in FlowTux
The ServiceNow plan, step by step
- Scope the tablesUsually incident and sc_req_item. Leave change_request, problem and the cmdb_ci tables where they are.
- Check your rate-limit rulesAsk your ServiceNow admin which rules in sys_rate_limit_rules apply to the export user, and whether the 10,000-row export properties were changed.
- Pull records with display valuesPage /api/now/table/incident with sysparm_display_value=all so callers and groups arrive as names and emails, not bare sys_ids.
- Pull journals separatelyQuery sys_journal_field by element_id for each record. comments become thread comments; work_notes become internal notes.
- Send the export; we map itWe map your state and priority choices, keep INC and RITM numbers, and check counts per state and per month against ServiceNow.
- Make FlowTux the front doorPoint Slack and email intake at FlowTux and run both for two weeks. Changes and CMDB lookups keep happening in ServiceNow.
Run both. Decide with data.
The risk in switching helpdesks is not the import. It is committing before you know whether the AI actually closes your tickets. So keep ServiceNow running, send new tickets to FlowTux, and compare the two queues on live traffic for two weeks. If the numbers do not justify the move, you have lost two weeks and no data.
How long it takes
API throughput is whatever your instance’s rate-limit rules allow, which only your admin can tell you. The parallel run is two weeks. ServiceNow itself does not get switched off as part of this.
Migration help is included: we do the import and the field mapping with you on a call, at no extra cost and on every plan. There is no self-serve importer, so nothing loads until you have seen the mapping.
Related
ServiceNow migration FAQ
Can we move everything off ServiceNow to FlowTux?
No, and we do not suggest it. FlowTux replaces the incident and request front door. Change management, problem management and the CMDB stay in ServiceNow.
Why do our ServiceNow exports stop at 10,000 rows?
ServiceNow sets a 10,000-row default for each export format through properties such as glide.csv.export.limit. Use the Table API for larger pulls, or ask your admin about the property.
How do we get comments and work notes out?
They are journal entries in sys_journal_field, not columns on the incident. Query that table by the record’s sys_id. ServiceNow documents that the XML URL export leaves journal fields out.
What happens to sys_id references?
Request display values from the Table API with sysparm_display_value=all, so each reference carries a readable name alongside the sys_id. Requesters are then matched by email.
Start with two weeks in parallel
Keep ServiceNow running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.