Pylon to eDesk migration requires a custom API-based ETL pipeline. The B2B-to-eCommerce data model shift means no direct import path exists, and rate limits on both sides constrain throughput.
There is no native migration path between Pylon and eDesk, and no third-party migration tool supports Pylon as a source as of July 2025. The fundamental challenge is a data model translation: Pylon is Account-centric with a nested Issue→Message→Thread structure tied to Slack channels, while eDesk is Order-centric with tickets linked to sales orders and marketplace channels. A custom API-based ETL pipeline is required, constrained by Pylon's 10–20 requests/minute rate limits and eDesk's 60 requests/minute account-wide ceiling, with eDesk API access restricted to the Enterprise plan only.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Marketing automation caveat
If the real goal is lead nurturing, pipeline management, or campaign automation, eDesk is the wrong system of record. Its data model centers on tickets, messages, contacts, sales orders, tags, templates, and custom fields — not CRM opportunities or marketing objects. (developers.edesk.com)
Account flattening is the biggest design decision
Pylon's Account object holds company-level data (health scores, CRM syncs, partner accounts, subaccounts). eDesk has no equivalent. You must decide whether to: (a) store Account names as a custom field on each ticket, (b) embed account data in internal notes, (c) keep it in your CRM, or (d) accept the data loss. Document this decision and get stakeholder sign-off before proceeding. (docs.usepylon.com)
Timestamp preservation
eDesk's Create Ticket API (POST /v1/tickets) and Create Message API both document a created_at field (developers.edesk.com), but you must verify with a single test ticket whether the provided value is respected or overwritten with the current server time. In our testing, the created_at value on the ticket was preserved, but updated_at was overwritten to the current time upon message creation. Losing historical timestamps is one of the most common traps in helpdesk migrations — always verify in your specific eDesk instance before running the full migration.
Rate limit math matters. If each Pylon Issue has an average of 5 messages, migrating 1,000 issues requires
- 1,000 ticket creation calls - 5,000 message creation calls - ~1,000 customer creation/lookup calls - Total: ~7,000 API calls to eDesk At 60 req/min, that is ~117 minutes of continuous API traffic — assuming zero errors or retries. In practice, plan for 2–3x actual wall time due to retries, validation lookups, and error handling. Scaling estimates: | Issues | Avg msgs/issue | Total API calls | Minimum time | Realistic time | |--------|---------------|-----------------|-------------|----------------| | 1,000 | 5 | ~7,000 | 2 hrs | 4–6 hrs | | 5,000 | 5 | ~35,000 | 10 hrs | 20–30 hrs | | 10,000 | 5 | ~70,000 | 19 hrs | 38–60 hrs | | 10,000 | 5 (elevated limit) | ~70,000 | 5–8 hrs | 8–15 hrs | Request a rate limit increase from eDesk support before any migration above 5,000 issues.
Confirmed data loss scenarios
The following Pylon data types will not survive the migration to eDesk in their original form. Document these in your migration plan and get stakeholder sign-off before proceeding:
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Pylon
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm eDesk can hold your support model
Walk your current workflow through eDesk: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Pylon → eDesk timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Pylon → eDesk specifics
- Channel pivot to eCommerce
- A company evolving from B2B SaaS support to direct-to-consumer or marketplace selling needs order-aware tooling. eDesk pulls order numbers, tracking data, and customer purchase history into every ticket natively — something Pylon does not do.
- Marketplace compliance
- Amazon, eBay, and Walmart enforce strict SLA response windows (Amazon requires responses within 24 hours; eBay within 24–48 hours depending on the query type). eDesk's native integrations track these SLAs automatically and surface breach risk. Pylon has no marketplace integration layer.
- Cost consolidation
- Teams running Pylon for support alongside a separate eCommerce helpdesk can consolidate into eDesk for a simpler, single-platform operation. eDesk publishes standard plan pricing starting at $89/agent/month for the Professional tier, with API access restricted to the Enterprise tier. (edesk.com)
- Small team, < 500 issues, simple fields
- API-to-API migration script with basic rate-limit handling.
- Mid-market, 500–10,000 issues
- API-to-API migration script with exponential backoff, staging database, and validation queries.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Pylon export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Pylon export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Pylon where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Pylon → eDesk specifics
- Issues search
- POST /issues/search — 10 req/min, 30-day window max per query. For multi-year histories, iterate in 30-day windows.
- Contacts
- GET /contacts or POST /contacts/search — 60 req/min
- Accounts
- GET /accounts — 60 req/min, cursor-paginated with limits up to 1,000
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Pylon → eDesk field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Pylon → eDesk field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where eDesk has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
-
Convert Slack markdown to standard HTML
eDesk's UI renders HTML. Use the conversion function above as a starting point.
Data Format Converter Reshape the export into the format eDesk's importer expects -
Map Pylon User IDs to eDesk Agent IDs
using a pre-built lookup dictionary (match by email address).
-
Handle missing email addresses
for Slack-only contacts (see Edge Cases section).
Pylon → eDesk specifics
- Custom Fields
- GET /custom-fields — per object type (account, issue, contact)
- Strip Slack-specific mention tags
- (e.g., <@U123456>) — otherwise eDesk tickets will be littered with unreadable user IDs. Replace with [user:U123456] or resolve to display names via Slack's API.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a eDesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a eDesk sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under eDesk's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Pylon → eDesk specifics
- Separate test account
- Create a second eDesk account on the Enterprise plan specifically for migration testing. This incurs additional cost but provides full isolation.
- Tag-and-delete approach
- Run test imports into your production account with a migration-test tag, validate, then bulk-delete tagged tickets via the API before running the real migration.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in eDesk, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Pylon stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from eDesk's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Pylon and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Pylon read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Pylon → eDesk specifics
- Before migration
- Perform your initial migration into an eDesk test account or use the tag-and-delete approach
- Tag migrated records
- Add a pylon-migrated tag to all imported tickets for easy identification and bulk operations
- If mapping is flawed
- Delete all tagged tickets and adjust your transformation logic before retrying
- Post-rollback
- Verify ticket count is zero for the migration tag, then re-run the corrected pipeline
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Pylon and eDesk record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in eDesk, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Pylon read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
-
Validate attachment sizes
against eDesk's 10MB limit before loading.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Object Equivalent
| Pylon field | eDesk field | Notes |
|---|---|---|
| Account | ❌ No direct equivalent | eDesk has no company/organization object. Account-level data must be flattened into customer records, ticket custom fields, or internal notes. |
| Contact | Customer | eDesk customers are identified by email. One Pylon Account with 5 Contacts becomes 5 separate eDesk Customers. |
| Issue | Ticket | Direct mapping. Pylon Issue status → eDesk Ticket status. |
| Message (customer reply) | Message (inbound) | Maps to eDesk inbound message on ticket. |
| Message (agent reply) | Message (outbound) | Maps to eDesk outbound message. |
| Internal Note | Internal Note | eDesk supports internal notes on tickets. |
| Tag | Tag | Must pre-create tags in eDesk (with Tag Groups if needed). |
| Custom Field (Issue) | Custom Field (Ticket) | Type mapping required — Pylon types must match eDesk types (Text, Date, Select, Number, Yes/No, URL, Email). |
| Custom Field (Account) | Custom Field (Ticket) or lost | eDesk has no account-level custom fields. Flatten to ticket-level or store in notes. |
| Custom Object | ❌ Not supported | eDesk has no custom object support. Flatten to custom fields, export separately, or store as structured internal notes. |
| Knowledge Base Article | ❌ No native KB | Migrate to a separate KB tool (Zendesk Guide, Notion, Confluence) or accept the loss. |
| Feature Request | ❌ No equivalent | Export for archival; eDesk has no feature request tracking. |
| Survey / CSAT | ❌ No direct import | eDesk has its own feedback system — historical CSAT data cannot be imported. |
| AI Account Intelligence | ❌ No equivalent | Health scores, AI summaries, and account-level sentiment are Pylon-specific. Archive as notes or discard. |
Issue Ticket
Pylon Issues are conversational and Slack-native with nested threading, requiring significant structural transformation to fit eDesk's email/marketplace-native ticket model with no bulk import endpoint available.
| Pylon field | eDesk field | Notes |
|---|---|---|
| id | Custom Field: pylon_id | Store Pylon ID for cross-reference and delta syncs |
| title | subject | Direct mapping; fallback to "Imported Thread" if null |
| status | status | Map: new/waiting_on_you → Open, waiting_on_customer → Pending, closed → Resolved. Test on_hold mapping in sandbox. (docs.usepylon.com) |
| assignee_id | owner_user_id | Map Pylon user IDs to eDesk user IDs. eDesk tickets have one assigned owner — Pylon team assignments and followers must collapse to a single owner. |
| account_id | Custom field or note | No direct equivalent in eDesk |
| requester_id | contact_id | Map Pylon contact to eDesk customer by email |
| created_at | created_at | Verify eDesk API preserves historical timestamps (see callout below) |
| updated_at | updated_at | May be overwritten by eDesk on import |
| tags [] | tags_ids [] | Pre-create tags, map by name to eDesk tag IDs |
| custom_fields [] | custom_fields [] | Map field IDs; validate type compatibility |
| priority | Custom field or tag | eDesk has no native priority field — use tags or custom fields |
| message.body | message.body | Convert Slack markdown to HTML; strip <@U123456> mention tags |
| message.attachments [] | message.attachments [] | 10MB limit on eDesk; pre-scan and compress or host externally |
Pylon eDesk
| Pylon field | eDesk field | Notes |
|---|---|---|
| issue.id | Custom Field: pylon_id | For cross-reference and delta syncs |
| issue.title | ticket.subject | Fallback to "Imported Thread" if null |
| issue.status | ticket.status | Map values (see field-level mapping above) |
| issue.assignee_id | ticket.owner_user_id | ID lookup required; match by email |
| issue.requester_id | ticket.contact_id | Match by email |
| issue.created_at | ticket.created_at | Verify preservation in test run |
| issue.tags [] | ticket.tags_ids [] | Name→ID lookup via pre-created tags |
| issue.custom_fields [] | ticket.custom_fields [] | Type-match required; verify enum values |
| issue.account_id | Custom Field: company | Account name lookup from staging DB |
| issue.priority | Custom Field: priority | No native priority in eDesk |
| message.body | message.body | Strip Slack formatting, convert to HTML |
| message.attachments [] | message.attachments [] | 10MB limit on eDesk; pre-scan sizes |
| message.is_internal | message.type | true → "Note", false → "Message" |
| message.sender_type | message.direction | Customer → "Incoming", Agent → "Outgoing" |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets (Issues) | high | Pylon Issues are conversational and Slack-native with nested threading, requiring significant structural transformation to fit eDesk's email/marketplace-native ticket model with no bulk import endpoint available. |
| Contacts / Customers | medium | Pylon Contacts are tied to company-level Accounts with CRM-synced metadata, while eDesk uses flat, email-based Customer records, so hierarchical relationships and account intelligence data will be lost. |
| Message History | high | Preserving full message threading, timestamps, and internal notes requires per-message API calls on both sides, and Pylon's Slack-thread context may not map cleanly into eDesk's message structure. |
| Attachments | medium | Attachments require separate download and re-upload operations with eDesk enforcing a 10MB size limit, and inline images are not supported by eDesk's import mechanisms. |
| Custom Fields | high | Pylon's Custom Fields and Custom Objects must be manually mapped to eDesk's limited field types (Text, Date, Select, Number, Yes/No, URL, Email), with no automated import path for custom field configurations. |
| Tags | medium | Pylon uses flat tags while eDesk supports Tags and Tag Groups, and third-party tools cannot import tags automatically, requiring custom scripting for tag migration and re-organization. |
| Knowledge Base Articles | high | eDesk has no native knowledge base, so Pylon's KB articles and collections cannot be migrated to an equivalent destination and must be redirected to a separate third-party KB tool. |
| Automations and Triggers | high | Pylon's condition-based triggers must be manually recreated as eDesk Rules or HandsFree automations, with no import path and fundamental differences in automation architecture. |
| Accounts / Organizations | high | Pylon's Account model with health scores, AI summaries, subaccounts, and CRM sync fields has no equivalent in eDesk, meaning company-level grouping and account intelligence data cannot be preserved. |
| Priority Field | low | eDesk lacks a native priority field, but Pylon priority values can be mapped to eDesk tags or custom fields with relatively straightforward transformation logic. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Account-Centric to Order-Centric Translation
Pylon organizes all Issues under company-level Accounts with CRM-synced metadata, while eDesk links tickets to individual customers and sales orders, requiring a fundamental restructuring of entity relationships.
Nested Thread Structure Mapping
Pylon's Issue→Message→Thread conversational model, especially Slack-native threads, must be flattened or re-sequenced into eDesk's simpler per-ticket message structure without losing context.
Severe API Rate Limits
Pylon's Issues search endpoint is limited to 10 requests per minute and eDesk caps at 60 requests per minute account-wide with no bulk import endpoint, meaning a 10,000-issue migration requires 6–10 hours of continuous API calls.
Enterprise Plan API Gating
eDesk restricts API access to its Enterprise tier, so organizations on lower-cost plans cannot programmatically import data and must upgrade before any automated migration can proceed.
Custom Objects and Fields Incompatibility
Pylon supports Custom Objects on its Enterprise plan, while eDesk only supports a limited set of Custom Field types (Text, Date, Select, Number, Yes/No, URL, Email), requiring custom objects to be flattened into fields or ticket notes.
No Third-Party Tool Support
As of July 2025, no major third-party migration service (Help Desk Migration, Migrations Wizard) lists Pylon as a supported source, eliminating low-code migration options and necessitating custom development.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate data from Pylon to eDesk directly?
No. There is no native import path between Pylon and eDesk. You need a custom API-based ETL pipeline, a third-party migration tool (if one supports Pylon as a source), or a managed migration service. Both platforms have REST APIs that can be used for extraction and loading, but no built-in migration bridge exists.
What data is lost when migrating from Pylon to eDesk?
eDesk cannot replicate Pylon's Custom Objects, Knowledge Base articles, Feature Requests, Account hierarchy (partner/sub-accounts), Slack thread formatting, historical CSAT/survey data, notebooks, highlights, or account-level custom fields. These must be exported separately, flattened into ticket custom fields, or documented as accepted losses.
How long does a Pylon to eDesk migration take?
A migration of 1,000 issues with an average of 5 messages each requires approximately 6,000 eDesk API calls. At eDesk's 60 requests per minute rate limit, that is about 100 minutes of continuous API traffic. In practice, expect 2–3x that due to retries, validation, and error handling. A full migration typically takes 5–10 business days including planning, test runs, and validation.
What are the API rate limits for Pylon and eDesk?
Pylon enforces per-endpoint limits: Issues search at 10 requests per minute, issue messages at 20 per minute, and contacts/accounts at 60 per minute. eDesk allows 60 requests per minute account-wide, with a restoration rate of 2 requests per second after hitting the cap. Neither platform offers a bulk import API. eDesk API access requires the Enterprise plan.
Does eDesk support custom objects or accounts like Pylon?
No. eDesk supports custom fields on tickets (Text, Date, Select, Number, Yes/No, URL, Email types) but has no custom object support and no company/organization object. Pylon's Custom Objects must be flattened into custom fields, stored as internal notes, or exported to a separate system. Account-level data must be handled similarly.