Migrate from TOPdesk to ServiceNow

MIGRATION OVERVIEW

Why teams migrate from TOPdesk to ServiceNow

Migrating from TOPdesk to ServiceNow is a medium-to-high complexity data model translation project with no native migration path between the two platforms. The fundamental challenge lies in converting TOPdesk's flat asset records into ServiceNow's relational CMDB with class assignments and dependency mapping, while also reconciling differences in user models, incident history structures, and picklist value systems. Custom API scripting is required for extraction (TOPdesk's paginated REST API with separate endpoints per entity) and transformation, and all automation—including Action Sequences, SLA policies, and escalation rules—must be manually rebuilt in ServiceNow using Flow Designer and native SLA Definitions.

KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a TOPdesk to ServiceNow migration.

Most Critical

Flat Assets to Relational CMDB

TOPdesk stores assets as flat records with simple linking, while ServiceNow requires each asset to be classified into a specific CI class (e.g., cmdb_ci_server) with explicit relationship records mapped to types like 'Runs on' or 'Depends on'.

Incident Progress Trail Conversion

TOPdesk stores incident updates in a separate progress trail endpoint with rich text formatting that must be sanitized and remapped to ServiceNow's journal fields (work_notes and comments), which support only a limited HTML subset.

Picklist and Value Translation

TOPdesk uses named enum values for status, priority, and category fields, while ServiceNow uses integer-based choice lists, requiring a complete value-to-value translation table for every picklist field before migration.

Automation and SLA Rebuild

TOPdesk Action Sequences, SLA definitions, escalation rules, and event triggers have no export mechanism and must be documented and rebuilt natively in ServiceNow using Flow Designer and SLA Definitions, consuming 20-40% of total project effort.

Paginated Multi-Endpoint Extraction

TOPdesk's API limits incident responses to 100 records per page and requires separate API calls per incident for progress trails, actions, time spent, and attachments, creating hundreds of thousands of API calls for large datasets.

User Model Unification

TOPdesk separates Persons (callers) from Operators (agents) across distinct API endpoints, while ServiceNow unifies both into the sys_user table with role-based differentiation, requiring careful identity deduplication and role assignment during transformation.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from TOPdesk to ServiceNow and built proven solutions for each one.

Migration Challenge ClonePartner Status

High Complexity —

Solved

CMDB / Assets

TOPdesk's flat asset records must be classified into specific ServiceNow CI classes with dependency relationships defined, and loading them into incorrect tables will break Dependency Views and CI relation formatters entirely.

Solved

CI Relationships

TOPdesk asset links and assignments must be translated into explicit ServiceNow cmdb_rel_ci relationship types (Runs on, Hosted on, Depends on), with no automated mapping available between the two relationship models.

Solved

Automations & SLA Policies

Action Sequences, SLA definitions, escalation rules, and event triggers cannot be exported from TOPdesk and must be fully rebuilt in ServiceNow, with complex environments requiring 1-2 weeks of dedicated rebuild effort.

Solved

Custom Engineering —

Handled

Incidents

Core incident records map to ServiceNow's incident table, but progress trail entries, actions, requests, time spent, and attachments each require separate API extraction and careful remapping of status values and journal fields.

Handled

Users (Persons & Operators)

Merging TOPdesk's separate Persons and Operators into ServiceNow's unified sys_user table requires email-based coalescing, role assignment for agents, and preservation of legacy TOPdesk IDs for inactive users and historical references.

Handled

Changes

TOPdesk change activities map to ServiceNow Change Tasks, but template-driven activities need manual recreation and linked assets must be re-associated after load.

Handled

Knowledge Articles

Category structures differ between platforms, inline images require re-hosting to ServiceNow's attachment system, and HTML formatting from TOPdesk often requires cleanup to render correctly.

Handled

Attachments

Attachments must be downloaded as binary content per-record from TOPdesk and uploaded individually to matching ServiceNow records, creating significant API overhead and requiring careful parent record sys_id mapping.

Handled

Clean Transfer

Groups & Memberships

Operator Groups map to sys_user_group with memberships rebuilt via sys_user_grmember records, which is straightforward but must be completed before transactional records are loaded to ensure assignment references resolve correctly.

Clean

Time Registrations

Time registrations map to ServiceNow time_card or task_time_worked records, but must be linked back to the correct migrated incident or change sys_id, requiring a consistent operating model decision upfront.

Clean

3 high-complexity solved

5 custom-engineered

2 clean transfers

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from TOPdesk to ServiceNow exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your TOPdesk to ServiceNow migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new ServiceNow, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Pros and cons of different migration options

Choosing the right approach is key because migrating from TOPdesk to ServiceNow isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited SLA
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / SLA predictability	✓ Predictable SLAs	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The TOPdesk and ServiceNow APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving conversation threads, attachments, and internal notes
Syncing custom fields, SLAs, and macros without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your TOPdesk data and ServiceNow
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure TOPdesk or ServiceNow exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

Custom fields, ticket forms, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for CRMs, chat, or feedback tools

The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from TOPdesk to ServiceNow. Can't find what you're looking for? Talk to our team.

How long does a TOPdesk to ServiceNow migration take?

A typical TOPdesk to ServiceNow migration takes 2 to 5 weeks end-to-end. Small environments under 10,000 incidents with no CMDB can complete in under 2 weeks. Enterprise environments with 100,000+ records, complex CMDB relationships, and large attachment volumes typically require 4 to 8 weeks including UAT and cutover.

What data cannot be migrated from TOPdesk to ServiceNow?

TOPdesk Action Sequences, SLA definitions, mail import rules, custom form layouts, dashboard configurations, and operator permission structures cannot be exported via API. These must be manually documented and rebuilt in ServiceNow using Flow Designer, SLA Definitions, and native configuration tools.

Can TOPdesk incident history be preserved in ServiceNow?

Yes. TOPdesk progress trail entries can be extracted via the Incident Management API v4 endpoints and loaded into ServiceNow as work_notes or additional_comments journal entries. Rich text formatting may be simplified due to differences in supported HTML between platforms.

Can TOPdesk asset relationships be preserved in ServiceNow CMDB?

Yes, but TOPdesk assets must be classified into ServiceNow CI classes and relationship records must be explicitly created in the cmdb_rel_ci table. Dumping flat asset records without classification and relationship mapping results in a CMDB with no operational value.

Is there downtime when migrating TOPdesk to ServiceNow?

With proper planning, downtime can be reduced to a 2 to 4 hour cutover window. Migrate historical data in advance, run the service desk on TOPdesk during migration, and perform a final delta sync before switching over.

How long does the TOPdesk to ServiceNow migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will my team lose access to TOPdesk during the migration?

No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.

Will there be downtime when migrating from TOPdesk to ServiceNow?

No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.

Do I need professional help for this migration?

While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your TOPdesk→ServiceNow migration.

Contact our team

Ready to start your
ServiceNow Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.

Migrate from TOPdesk to ServiceNow with precision & ease

Why teams migrate from TOPdesk to ServiceNow