ServiceNow Data Migration Specialist

Job Description
ServiceNow Data Migration Specialist
BMC Remedy to ServiceNow Migration
Job Title
ServiceNow Data Migration Specialist
Project
BMC Remedy to ServiceNow — Data Migration
Engagement Type
Contract / Project Based
Location
Remote / Client Site (KSA)
Experience
3–6 Years
Notice Period
Immediate to 2 Weeks Preferred
1. Role Overview
We are looking for an experienced ServiceNow Data Migration Specialist to join the project team. The
candidate will be responsible for end-to-end migration of legacy data from BMC Remedy into the
ServiceNow platform, covering multiple ITSM modules including Incidents, Change Requests, Problems,
Known Errors, SLAs, Work Logs, and Attachments.
The role requires deep hands-on expertise in ServiceNow Import Sets, Transform Maps, JDBC
connections, scripted data transformation, and REST API integrations. The candidate must be
comfortable working independently on complex data challenges and collaborating with technical leads
and project managers in an agile environment.
2. Key Responsibilities
2.1 Data Migration Design & Execution
Design and implement end-to-end Remedy-to-ServiceNow data migration strategy
across 19+ modules
Configure and manage JDBC data sources in ServiceNow to extract data directly from
Remedy backend databases
Build Import Set tables and fully scripted Transform Maps (onBefore scripts) for each
migration module
Implement composite coalesce logic to prevent duplicate record insertion across
multiple JDBC re-runs
Handle epoch-to-GlideDateTime conversions, GlideDuration field mappings, and
Percent Complete field type considerations
Migrate historical timestamps with backdating using autoSysFields(false) and
setWorkflow(false)
2.2 Module-Specific Migration
Incidents — full field mapping including state, priority, category, assignment group, work
notes, and SLA linkage
Change Requests (CRQ) — complete migration with approval records, CAB mappings,
and work log history
Change Approvals — sysapproval_approver mapping with individual vs group approver
resolution logic
SLA (task_sla) — mapping of stage, has_breached, active, duration, elapsed time,
business time left, percent complete fields; auto-creation of SLA definitions
(contract_sla) when not found
Problem Investigation (PBI) — parent problem record migration with state mapping
Known Error (PKE) — migration into problem_task table with correct model type and
parent-child linkage
Work Logs — backdated journal entries into sys_journal_field and sys_history_line
Attachments — REST API-based attachment pull from Remedy with on-demand UI
Action and background scheduled job architecture for 6.5M+ records
2.3 Data Quality & Validation
Perform field-level data comparison between Remedy source and ServiceNow migrated
records
Build validation reports to identify and resolve field mapping mismatches
Implement status flags (pending, completed, failed, on_demand) for attachment
migration queue tracking
Analyse and resolve JDBC encoding issues including Arabic filename handling and
UTF-8 charset configuration
Cross-validate approval status mappings, SLA measurement status codes, and
timestamp accuracy
2.4 Architecture & Integration
Design permanent attachment migration queue table (u_attachment_migration_queue)
to replace short-lived staging tables
Build on-demand UI Action for customer-triggered attachment retrieval from Remedy
REST API
Configure scheduled jobs with batch size control and retry logic (max 3 retries) for
background attachment migration
Handle executeAsync() + waitForResponse() + saveResponseBodyAsAttachment()
pattern for binary attachment transfer via ECC Queue
Manage MID Server assignments across 4 MID Servers for production migration of
~37.8 million records
2.5 Collaboration & Documentation
Work closely with Technical Lead, Project Manager, and client stakeholders to clarify
scope and resolve data ambiguities
Document field mappings, transformation logic, coalesce keys, and migration decisions
Prepare and maintain migration execution plans with phased timelines and risk registers
Provide effort estimates for migration modules and flag blockers proactively

• 5. What You Will Work On
• This is not a simple configuration role. You will be working on one of the largest Remedy-to-ServiceNow
• migrations in the region, involving:
• Scale
• Complexity
• Modules
• 37.8 million records across 19
• modules
• 4 MID Servers Parallel
• processing
• INC, CRQ, PBI, PKE SLA,
• Approvals, Attachments
• 6.5M attachments via REST
• API
• On-demand + background job
• architecture
• Work Logs, Known Error
• Problem Tasks
• 6. Soft Skills
• Strong problem-solving mindset — ability to reverse-engineer Remedy data structures
• without documentation
• Self-driven — comfortable working with minimal hand-holding in ambiguous situations
• Clear communicator — able to explain technical blockers to non-technical stakeholders
• Detail-oriented — data migration leaves no room for guesswork
• Team player — collaborate with Technical Lead, PM, and client-side Remedy team
• 7. Engagement Details
• Duration
• 6–12 Months (extendable)
• Start Date
• Immediate
• Work Mode
• Remote with occasional client site visits (KSA)
• Reporting To
• Technical Lead / Project Manager