Launched:self-serve migrations intoSuperhuman Docs (Coda)
Try it now
01Agent-first
Runs where you already work
Plug it into Claude, ChatGPT or Cursor. Describe the move in plain English; the agent runs it.
02Engineer-led
Our production engine, unlocked
The pipeline our engineers use on managed enterprise migrations — the same code, now something you can drive yourself.
03Pricing
Try 10 pages free, then $1 a page
Credit-based, pay-as-you-go. No scoping call, no quote — sample it on your own docs before you spend anything.
04Sources
NotionSlabConfluenceSoonGoogle DocsSoon
Skip to content

Epicor On-Premises Sunset: Final Releases & Data Migration

Epicor's final on-premises releases for Kinetic, Prophet 21, and BisTrack land between 2026–2028. Here are the published dates, support phases, and how to extract your data.

Roopendra Talekar Roopendra Talekar · · 15 min read
Epicor On-Premises Sunset: Final Releases & Data Migration
TALK TO AN ENGINEER

Planning a migration?

Get a free 30-min call with our engineers. We'll review your setup and map out a custom migration plan — no obligation.

Schedule a free call
  • 1,500+ migrations completed
  • Zero downtime guaranteed
  • Transparent, fixed pricing
  • Project success responsibility
  • Post-migration support included

Epicor On-Premises Sunset: Final Releases & Data Migration

Epicor is ending on-premises feature development for Kinetic, Prophet 21, and BisTrack. On January 6, 2026, the company published the schedule of final on-premises releases: BisTrack Desktop 2026.2 (tentatively December 2026), Kinetic 2028.1 (January 2028), and Prophet 21 2028.1 (May 2028). Future innovation for these platforms moves exclusively to the Epicor Cloud (epicor.com).

Your on-premises system will not stop working overnight. But the planning window is now open — and the earlier you scope data extraction and migration, the more options you keep.

This guide covers the exact timelines Epicor published, what the support phases actually include, your three realistic options, and how to get data out of Epicor's SQL Server databases cleanly.

What did Epicor announce on January 6, 2026?

Epicor announced the schedule of its final on-premises feature releases for three products: Epicor Kinetic, Epicor Prophet 21, and Epicor BisTrack. The announcement explicitly states that these releases "mark the transition of future innovation for these platforms exclusively to the Epicor Cloud." (Epicor press release, January 6, 2026)

Two things the announcement does not say:

  • It does not set an end-of-life date. Epicor's own wording describes an end of on-premises feature development, followed by defined support phases — not a shutdown date.
  • It does not name Eclipse. The January 6, 2026 announcement covers Kinetic, Prophet 21, and BisTrack only. Eclipse customers should ask their Epicor account team for roadmap status.
Info

All dates below are from Epicor's press release of January 6, 2026 (epicor.com). Epicor describes the final-release dates as tentative. It does not mark the support dates as tentative.

Every Epicor on-premises deadline in one table

Product Final on-prem release Tentative date Active Support ends Sustaining Support begins
Kinetic 2028.1 January 2028 December 31, 2029 January 1, 2030
Prophet 21 2028.1 May 2028 June 30, 2029 July 1, 2029
BisTrack Web Browser & API 2028.1 July 2028 June 30, 2029 July 1, 2029
BisTrack Desktop 2026.2 December 2026 December 31, 2028 January 1, 2029
BisTrack UK 3.9 — — December 31, 2026 January 1, 2027

The gap between each final release and the end of Active Support varies by product. Kinetic customers get close to two years of Active Support after their final release. Prophet 21 customers get about 13 months, and BisTrack Web Browser & API customers about 12 months. BisTrack Desktop customers get two years of Active Support, but the clock starts much sooner — the final Desktop release lands in December 2026.

Sustaining Support duration: Epicor's January 2026 announcement does not state when Sustaining Support ends — it does not define a fixed termination date for any product. This is the most practically important missing variable for customers evaluating "stay on-premises" as a long-term option. Before treating Sustaining Support as an indefinite runway, ask your Epicor account team for the contractual end date and what the wind-down process looks like.

BisTrack UK 3.9: what it is and why it matters

Epicor's announcement lists BisTrack UK 3.9 as a 2017 release. Active Support for UK 3.9 ends December 31, 2026 — the earliest support deadline in the January 2026 announcement (epicor.com). If you run BisTrack UK 3.9, your planning horizon is effectively immediate.

Why BisTrack Desktop is the most urgent for North American customers

BisTrack Desktop 2026.2 is the earliest final release in Epicor's schedule, tentatively December 2026. If you run BisTrack Desktop in a lumber, building materials, or LBM distribution environment, your planning horizon is shorter than every other Epicor product line. Active Support ends December 31, 2028 — roughly two years from the final release.

The SQL Server 2019 convergence

One timing convergence worth flagging: if your Kinetic database runs on SQL Server 2019, Microsoft's extended support for SQL Server 2019 ends January 8, 2030 (learn.microsoft.com) — eight days after Epicor's Active Support for Kinetic 2028.1 ends on December 31, 2029. Both expiry clocks hit within eight days of each other. Organizations that delay Kinetic planning until late 2029 will face simultaneous ERP and database platform decisions under time pressure.

What does Active Support vs Sustaining Support actually cover?

Active Support is Epicor's full support tier. CIO.com describes it as full access to Epicor phone support, security updates, and new issue investigation (cio.com).

Sustaining Support is a reduced tier. Press coverage by Enterprise Times (enterprisetimes.co.uk) and CIO.com (cio.com) describes it as:

  • Limited phone support
  • Access to the online knowledge base
  • Access to the latest release, but not to new modules

Per Enterprise Times, Sustaining Support does not include new features, comprehensive bug fixes, or the sale of new modules. Neither report lists regulatory or compliance updates under Sustaining Support.

Warning

Epicor's public announcement does not itemize support phase contents in granular contractual detail. The descriptions above are drawn from third-party reporting. Request the specific support terms applicable to your contract — in writing — before making a migration or stay-on-premises decision. Also ask explicitly: when does Sustaining Support end?

What a final feature release means for your infrastructure

A final feature release is a development freeze. After the specified version, Epicor will no longer build new modules, API endpoints, or functional capabilities for the on-premises codebase. The release moves through Active Support and then Sustaining Support, but the architecture is effectively locked.

This creates compounding technical debt in two specific areas:

  1. Third-party integrations. As connected tools — CRMs, warehouse management systems, shipping providers, payment processors — update their APIs, your frozen on-premises ERP may lack support for modern authentication protocols (OAuth 2.0, PKCE flows) or new webhook structures. Integrations that work today will degrade as the surrounding ecosystem moves forward.
  2. Customizations and middleware. Internal scripts, Service Connect workflows, middleware relying on the on-premises API, SSRS reports that query the database directly, BAQs feeding downstream systems, and direct-SQL integrations all become harder to maintain on a frozen codebase. Each surrounding system upgrade creates a new potential incompatibility.

The longer an on-premises system runs past its development freeze, the larger those integration gaps become at migration time.

Three realistic options for Epicor on-premises customers

Every on-premises Epicor customer now faces a three-way decision. In every path, getting the data right is the part that most frequently causes overruns.

Option 1: Move to Epicor Cloud

Epicor's intended path. Epicor's Ascend with Epicor program offers a migration methodology, business planning support, AI tooling, and consulting, and lets customers generate a readiness assessment of their environment (epicor.com). Epicor says qualified businesses can go live in as little as 90 days (epicor.com).

The technical reality of cloud migration:

  • REST API v2 integrations built against on-premises Kinetic are the most portable. Expect to change the base URL and credentials.
  • What does not carry over: anything that bypasses the API layer — direct SQL reads or writes against the SQL Server database, Service Connect workflows running on the Epicor application server, SSRS reports that query the database directly, and any ETL jobs using ODBC/OLEDB connections to Epicor's SQL instance.

If your Kinetic or P21 environment runs heavy direct-SQL integrations, inventorying and rebuilding those is the dominant technical effort — not the data migration itself.

Option 2: Re-platform to a different ERP

Some manufacturers and distributors will use this forcing event to evaluate alternatives — Dynamics 365 Business Central, Oracle NetSuite, Acumatica, SAP Business One, or IFS. The data extraction problem is identical regardless of the target: you need clean, complete data out of Epicor's SQL Server, transformed to match the target system's schema.

A note on scope: a full ERP re-platform is your own implementation project, and its length depends on your company and the target system. The data migration we perform is one component of that project, not the whole project. Most data migrations are completed within 1–5 business days, depending on data volume, complexity, and API rate limits.

For product comparisons, see SYSPRO vs Epicor Kinetic: Which to Choose in 2026 and IFS vs Epicor Kinetic: Architecture, TCO & Migration Guide.

Option 3: Stay on-premises in Sustaining Support

Your on-premises system does not shut down when Active Support ends. Sustaining Support continues with limited assistance. Organizations with stable, well-understood Epicor environments, minimal third-party integration complexity, and no near-term regulatory requirements may find this viable for some period after 2029/2030.

The risks are compounding, not static:

  • The precise scope of fixes under Sustaining Support is not publicly defined.
  • Regulatory and compliance updates (tax table changes, payroll updates, government reporting format changes) are not explicitly included under Sustaining Support.
  • The functional gap between on-premises Sustaining Support and cloud customers widens every quarter as Epicor invests exclusively in cloud features.
  • The duration of Sustaining Support is not publicly stated — ask Epicor for the contractual end date before treating this as an indefinite option.
  • Contractual considerations: customers on multi-year Epicor maintenance agreements may face terms or penalties relevant to migration or cancellation timing. Review your current maintenance contract before finalizing a timeline.

How to extract data from Epicor Kinetic and Prophet 21

Data extraction is the foundation of every path above. Both Kinetic and Prophet 21 sit on Microsoft SQL Server databases. On-premises, the data is accessible via direct SQL query, Epicor's REST API v2, or file exports.

Method 1: Direct SQL extraction (on-premises only)

Direct SQL queries the underlying database directly, bypassing the application layer. For on-premises installations, SQL Server Management Studio (SSMS) is the most complete extraction path.

Why direct SQL is often preferred for bulk extraction:

  • No application-level rate limits or pagination overhead
  • Avoids consuming IIS worker processes that keep the ERP running for active users
  • Avoids paging through large datasets one API request at a time

Kinetic schema basics:

Key navigational points in Kinetic's SQL Server database:

  • INFORMATION_SCHEMA.COLUMNS lists every table and field in the instance
  • Tables are prefixed by functional area: Erp.* for ERP data, Ice.* for framework/metadata
  • Common joins: Erp.Part → Erp.PartPlant (site-level inventory attributes), Erp.JobHead → Erp.JobOper (routing steps), Erp.OrderHed → Erp.OrderDtl (order lines)
  • Epicor's ICE schema documentation is available to licensed customers through the Epicor EpicCare portal; community schema discussions are on EpiUsers

Prophet 21 schema advantage: P21 ships with pre-configured SQL views that abstract the underlying table joins — a significant shortcut when extracting customer, item, vendor, and order history data compared to manually mapping Kinetic's raw tables.

Warning

Epicor's SQL schema has minimal database-level constraints — validation logic lives in the application layer, not in SQL foreign keys. Extracted data can contain orphaned references, soft-deleted records flagged by a boolean column rather than physical deletion, and values meaningful only in application context. Always validate extracted data against application-level business rules, not just row counts.

Method 2: Epicor REST API v2 (on-premises and cloud)

Epicor Kinetic's REST API v2 provides OData v4–compliant endpoints for Business Objects (BO), Business Activity Queries (BAQ), and Epicor Functions. Each request needs an API key (x-api-key) as well as user authentication.

For large volumes, REST extraction means paging through results request by request. Test page sizes and paging against your own instance before you plan a bulk extract around the API.

When the REST API is the right extraction method:

  • Extracting from Epicor Cloud, where direct SQL is not available by default
  • When you need data that respects application-level business logic and calculated fields
  • When existing BAQs already expose exactly the data sets you need, and those BAQs are tested and trusted
  • When record volumes are modest and speed is not the primary constraint

Method 3: CSV exports via BAQ

Business Activity Queries (BAQs) can export flat CSV files. CSV is the least preferred extraction format. Known failure modes:

  • Encoding errors when records contain special characters or non-ASCII text
  • Text field truncation at column width limits
  • Delimiter collisions when users have typed commas, pipes, or tab characters into free-text fields
  • Loss of data type fidelity (dates, decimals, booleans all become strings)

If you must use flat-file export, extract to JSON rather than CSV. JSON preserves data types and handles embedded special characters correctly.

Method 4: Epicor DMT and Data Extraction Tool

Epicor Data Management Tool (DMT) is designed to import data into Epicor — not to extract it. It imports Excel and CSV files and validates them against Epicor's business logic (epicor.com). Do not use DMT as an extraction mechanism.

Epicor Data Extraction Tool is a separate utility. Epicor describes it as extracting data from legacy Epicor ERP systems to Kinetic (epicor.com). It is part of Epicor's own Epicor-to-Epicor toolkit, not a path to non-Epicor targets.

What data should you actually migrate?

Not everything in your Epicor database belongs in the target system. Cloud ERPs typically charge on storage and user counts. Moving decades of obsolete history inflates implementation costs and degrades performance in the new system.

Standard migration scope:

Data category Migrate? Notes
Customers, vendors, suppliers Always Master record with all addresses, contacts, terms
Items / parts Always Including UOM, pricing, GL mappings
Bills of materials Always Full BOM structure including revisions
Routings Always Work center, operation, labor standard
GL chart of accounts Always With segment structure mapped to target
Price lists / contracts Always Pricing logic must be validated in target
Open sales orders Always Including lines, releases, shipping notes
Open purchase orders Always Including receipts in process
Open work orders / jobs Always With material and operation status
Open AP / AR Always With aging and payment terms
Closed transaction history Selective Typically 2–3 years for forecasting; archive older
GL journal history Selective Consult your auditor for retention requirements
Attachments / documents Selective Audit size and relevance; archive if >3 years old
UD tables / custom fields Map or archive Requires explicit mapping to target extensibility model
Soft-deleted / inactive records Rarely Validate business need before including

The 2–3 year closed transaction history guideline covers most demand planning and sales forecasting use cases. Specific industries (aerospace, defense, medical devices) may have regulatory retention requirements that override this — confirm with your compliance team before archiving.

For a detailed breakdown of this framework, see What Data Should You Actually Migrate to Your New ERP?.

The data migration: timeline, process, and validation

Data migration is the process of extracting records from the source system, transforming them to match the target system's schema and business rules, and loading them into the target. It is a distinct effort from the broader ERP implementation or cloud migration project. The implementation is your own project and runs on its own timeline. The data migration is measured in days.

How long does an Epicor data migration take?

Volume Typical elapsed time
Under 10,000 records Under 24 hours
Most migrations 1–5 business days, depending on data volume, complexity, and API rate limits

The bulk historical load runs during the working days before go-live, while your team keeps working in Epicor. On the go-live Monday, Epicor is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and people log in to the new system that morning.

These timelines describe the data migration component only — not the ERP implementation, re-platform, or configuration project surrounding it.

Validation and data integrity

ERP data is highly relational. A sales order cannot load into a target system without a valid customer ID, part number, tax schedule, and site location already present. Referential integrity failures — caused by migrating child records before parent records — are among the most common causes of migration rework.

A complete validation framework covers:

  • Referential integrity sequencing — parent records (customers, parts, GL accounts) must load before child records (orders, invoices, job operations). The dependency graph must be explicit before extraction begins.
  • Record-count parity — if 45,212 active parts exist in Epicor, 45,212 active parts must load into the target ERP.
  • Field-level spot checks — high-value fields (unit price, on-hand quantity, credit limit) are compared record-by-record between source and destination for a sample.
  • Checksum verification — total byte size and hash of the payload are compared between source and destination.
  • Business rule validation — extracted data is tested against target-system business logic, not just SQL constraints, before the full load runs.

Zero-downtime migrations: achieving true zero downtime requires the source system to support change-data-capture (CDC) or a reliable change-tracking mechanism. On-premises Kinetic supports CDC via SQL Server's native CDC feature if enabled. P21 also runs on SQL Server and supports CDC. If CDC is not enabled, a background sync approach with a final delta-sync cutover can minimize downtime to minutes rather than hours — but requires planning before migration begins.

Security, compliance, and chain of custody

When extracting data from an on-premises environment, the security perimeter temporarily extends to the migration provider. Evaluate any migration provider on these criteria:

  • Encryption standards: AES-256 at rest; TLS 1.2 or higher in transit (TLS 1.3 preferred)
  • Certifications: SOC 2 Type II (independently audited, not self-attested); ISO 27001
  • Data residency: Where is staging data stored? In what jurisdiction?
  • Retention policy: How long does the provider retain your data after project close? 30 days is a reasonable maximum.
  • Access controls: Who at the provider owns your project and can view your data?
  • Regulatory safeguards: GDPR DPA, CCPA disclosures, HIPAA BAA (if PHI is in scope). Note: HIPAA has no official certification scheme; a provider claiming "HIPAA certified" is using inaccurate terminology — verify they can describe specific technical safeguards instead.
  • Contractual protections: NDA and DPA executed before data transfer begins.

ClonePartner is independently audited for SOC 2 Type II and ISO 27001, with AES-256 at rest and TLS 1.2+ in transit. A dedicated engineer owns each project. Staging data auto-purges within 30 days of project close. We execute NDAs and DPAs on request and sign BAAs before handling PHI.

When to start planning — and why the window matters

Start now. Not because the deadline is imminent — Kinetic's Active Support runs through December 2029 — but because migration scoping reveals problems that take time to fix.

Recommended lead time: at least 3–4 months before your internal cutover target. That window is needed for:

  1. Data audit. Run record counts, identify orphaned and soft-deleted records, map custom UD fields and tables, assess data quality. On-premises customers can run this directly in SSMS against their SQL Server.
  2. Integration inventory. Catalogue every direct-SQL integration, every Service Connect workflow, every SSRS report, every ETL job. If moving to Epicor Cloud, anything bypassing the REST API will break and must be rebuilt.
  3. Scope decisions. Decide what to migrate versus archive. Historical transaction data, attachments, and deprecated custom tables should be evaluated — not defaulted to "migrate everything."
  4. Sample migrations. Extract a subset of master data and open transactions, transform to the target schema, and validate. This is where edge cases surface: encoding issues, orphaned references, fields with no equivalent in the target system.

Starting earlier means data quality problems can be fixed in the source system before cutover — not discovered during it. As the 2028–2029 Active Support deadlines approach, demand for qualified migration resources will increase.

The broader ERP end-of-support wave

Epicor is not moving in isolation. Mainstream maintenance for SAP Business Suite 7 core applications, including ECC 6.0, ends in 2027 (asug.com). Microsoft ended mainstream support for Dynamics NAV 2016 in April 2021 (learn.microsoft.com). If your organization also runs end-of-support Microsoft infrastructure — SharePoint Server 2016/2019, Dynamics GP, or Dynamics NAV — the migration planning windows overlap and should be coordinated.

For the broader end-of-support calendar, see Software End of Life 2026: The Complete EOL Calendar. For common failure modes in ERP data migrations, see Why ERP Migrations Fail at the Data Layer: 9 Core Patterns.

Decision framework: which path is right for your organization?

The three-option decision is not purely a data problem — but data complexity is the most reliable predictor of which path is feasible within a given timeline.

Factor Favor Epicor Cloud Favor re-platform Favor stay on-premises
Current Epicor version On supported version, minimal customization Heavily customized Epicor 9/10 or older Stable environment, minimal integrations
Integration complexity Mostly REST API integrations Many direct-SQL or legacy integrations Few external integrations
Regulatory exposure Needs ongoing compliance updates Needs compliance updates Minimal regulatory change anticipated
Budget horizon Can fund cloud migration now Can fund full re-platform Cannot fund migration in next 2–3 years
Sustaining Support duration — — Requires confirmed end date from Epicor
SQL Server version — — On SQL Server 2019: both expire within eight days (Dec 2029 / Jan 2030)

This table is a starting-point framework, not a decision algorithm. The correct path depends on factors specific to your organization, contract terms, and Epicor's response to questions about Sustaining Support duration.

Start with a scoping call, not a panic decision

The Epicor on-premises sunset is a forcing event, not an emergency — yet. Kinetic's Active Support runs through December 2029; BisTrack Desktop's runs through December 2028; BisTrack UK 3.9's ends December 2026. The first step is understanding what you have: how much data, in what shape, with what integrations.

Frequently Asked Questions

When does Epicor Kinetic on-premises support end?
Epicor Kinetic's final on-premises feature release is 2028.1, tentatively January 2028. Active Support for that release runs through December 31, 2029, and Sustaining Support begins January 1, 2030, per Epicor's January 6, 2026 announcement. Epicor has not announced an end date for Sustaining Support.
Is Epicor Prophet 21 being discontinued?
No. Prophet 21 continues as a product, but future innovation moves to Epicor Cloud only. The final on-premises P21 release is 2028.1, tentatively May 2028. Active Support for on-premises runs through June 30, 2029, and Sustaining Support begins July 1, 2029.
How do I extract data from Epicor Kinetic or Prophet 21?
On-premises, the most complete method is direct SQL queries via SQL Server Management Studio — both Kinetic and P21 run on Microsoft SQL Server. For cloud or API-preferred extraction, use Epicor's REST API v2 (OData v4 endpoints). Epicor also provides a Data Extraction Tool for moving legacy Epicor ERP data into Kinetic, and the Data Management Tool (DMT) for imports.
How long does an Epicor data migration take?
The data migration itself — extracting, transforming, and loading records into a target system — typically takes 1–5 business days depending on volume, complexity, and API rate limits. Small datasets under 10,000 records can finish in under 24 hours. This is separate from the broader ERP implementation project, which is a different timeline.
What is Ascend with Epicor?
Ascend with Epicor is Epicor's cloud migration program for customers moving to the Epicor Cloud. It combines a migration methodology, AI tooling, a readiness assessment of your environment, and consulting. Epicor says qualified businesses can go live in as little as 90 days.

More from our Blog