Time since we first saw it
Day 3
Early. Similar jobs usually come down between day 7 and day 50.
From 677 similar postings that came down. Coming down is not always a hire.
Work setup in the employer’s posting: RemoteFrom the employer’s posting
Employment type in the employer’s posting: ContractFrom the employer’s posting
Extract data from a custom SQL Server application and a legacy Sage BV environment
Build repeatable, script-driven conversion routines for test cycles and final cutover
Map legacy operations, resources and part groupings to the merged company's structure and Kinetic product groups
Load data mainly through DMT, using REST API or updatable BAQs where needed
Load historical transactions into a separate Kinetic archive instance after go-live
Extract data from two legacy sources: a custom on-premise SQL Server application covering BOMs, jobs, and operations, and a legacy Sage BV environment
Build repeatable, script-driven conversion routines that can be rerun across multiple test cycles and the final cutover.
mapping legacy operations and resources to the merged company’s structure and mapping legacy part groupings to Kinetic product groups and part classes
Load data primarily with DMT, using REST API, updatable BAQs, or other tools where needed.
Convert historical transactions into the Kinetic archive instance after go-live.
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Early. Similar jobs usually come down between day 7 and day 50.
From 677 similar postings that came down. Coming down is not always a hire.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
Our client, a global manufacturer of industrial processing equipment, is standardizing its operations on Epicor Kinetic under a common global design. Its Greater Toronto Area business recently merged three separate companies into a single operation. Two of those companies are already live on Kinetic. The third company’s finances are live on Kinetic, but its manufacturing operations still run on a legacy custom-built system that is being retired. We are looking for an experienced Kinetic developer to lead the data conversion that brings this final company fully onto the platform. You will work from existing functional and technical specifications, with oversight from the client’s Kinetic support lead, who knows the data and processes in depth. The work has two phases. First, you will convert master data and active transactions into the live production instance, transforming them to match global data standards. After go-live, you will load historical data as-is into a separate Kinetic archive instance used for reporting and transaction lookup. Key responsibilities: Extract data from two legacy sources: a custom on-premise SQL Server application covering BOMs, jobs, and operations, and a legacy Sage BV environment covering purchasing, sales orders, and financials, which may require report-based exports. Build repeatable, script-driven conversion routines that can be rerun across multiple test cycles and the final cutover. Apply documented transformation and mapping logic, including mapping legacy operations and resources to the merged company’s structure and mapping legacy part groupings to Kinetic product groups and part classes. Consolidate and validate inconsistent data, especially free-form units of measure and supplier records that overlap with existing master data. Load data primarily with DMT, using REST API, updatable BAQs, or other tools where needed. Make sure converted data merges cleanly into a live, multi-company environment without disrupting current operations, and that MRP produces reliable results. Convert historical transactions into the Kinetic archive instance after go-live. Support related development requests as needed, such as BPMs. Requirements Required: Extensive hands-on Epicor Kinetic experience, with multiple completed data conversions Strong SQL Server skills, including complex scripting, data transformation, and use of staging or mapping databases Deep experience with the Epicor Data Migration Tool (DMT) Proven experience converting data from non-Epicor or custom legacy systems Solid functional understanding of Epicor manufacturing, including BOMs, jobs, operations, resources, and MRP Experience cleansing and standardizing poor-quality legacy data Ability to work independently from functional and technical specifications Availability to commit full-time for the duration of the conversion Preferred: Experience loading data into an already-live Kinetic environment Experience converting historical transactional data into Epicor Experience extracting data from Sage BV or other non-SQL legacy systems Kinetic development skills, including BPMs, REST API, BAQs, SSRS, and dashboards Experience with multi-company or post-merger Epicor environments Comfort using AI tools to assist with data classification and cleanup
Complete your application on mainlinetalent.zohorecruit.com. The employer’s form will show what is required.
Already applied? Track this application
New Data Operations postings at the employers we follow are up 164% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Operations, by the work the posting describes.
Data operations staff do the day-to-day work of getting data processed correctly: loading and checking files, moving records between systems, fixing errors and following set procedures.
Expect Excel, some SQL, close attention to detail, and knowledge of the particular systems the company runs.
Data governance sets the rules for the data; data operations does the hands-on work of processing it and keeping it moving.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Location not supplied.
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.