Skip to content
Get a quote

Edicom EDI to Epicor Prophet 21 migration

We migrate Transaction Sets, Trading Partner configurations, Connection Protocols, and ERP Integration points from Edicom EDI into Epicor ERP (Kinetic and Prophet 21) with EDI maps inventoried for manual rebuild in Epicor Kinetic or AtlasExchange, VAN routing re-established per partner, and every country-specific e-invoicing mandate documented before cutover.

Short answer

FlitStack AI migrates edi document records, trading partner configurations, connection configurations, edi map rebuilds and epicor kinetic rest api / prophet 21 api integrations from Edicom EDI to Epicor Prophet 21, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 8-10 weeks.

By

Source Edicom EDI
DestinationEpicor Prophet 21
EDI Document RecordsTrading Partner ConfigurationConnection ConfigurationEDI Map RebuildEpicor Kinetic REST API / Prophet 21 API Integration
Mapped field by field · sample run · one-click rollback

What moves from Edicom EDI to Epicor Prophet 21?

Moving from Edicom EDI to Epicor ERP consolidates a two-vendor EDI-plus-ERP stack into a single platform with native EDI embedded directly in Epicor Kinetic and Prophet 21.

Read the full summary

Edicom EDI operates as a managed B2B integration layer supporting X12, EDIFACT, UBL, and ODETTE standards across 80+ countries; Epicor EDI uses AtlasExchange for managed services and native integration points for in-house ERP customers. We migrate Transaction Sets and Trading Partner records, rebuild Connection Protocol credentials (AS2, SFTP, VAN, OFTP2) in Epicor, and resolve ERP integration mapping between Edicom's document-transform logic and Epicor's order-to-cash and procure-to-pay flows. Country-specific e-invoicing mandates (Brazil NF-e, France Chorus Pro, Saudi ZATCA Phase 2) do not transfer between platforms and are itemized for re-implementation. Trading Partner re-onboarding with compliance testing is coordinated by tier (top-volume partners first) and runs in parallel before full cutover.

1:1

Transaction Sets → EDI Document Records (Epicor EDI)

Edicom EDI Transaction Sets (X12 850 purchase orders, 810 invoices, 856 ASN, 855 order acknowledgments, 997 functional acknowledgments; EDIFACT ORDERS, INVOIC, DESADV) map to Epicor EDI document records within the Epicor EDI module.

How it maps

We extract transaction history as structured export (XML/CSV) from Edicom, then load into Epicor Kinetic or Prophet 21 order, invoice, and ASN tables using Epicor's data import tools or REST API, preserving document numbers, dates, line items, and amounts. VAN interchange control numbers and functional acknowledgment status (997/Contrl) are stored as reference fields in Epicor EDI.

1:1

Trading Partners → Trading Partner Configuration (Epicor EDI)

Each Trading Partner record in Edicom EDI defines document types exchanged, communication protocol, and partner-specific validation rules.

How it maps

We export partner records as structured configuration files, then map each to Epicor EDI's Trading Partner module by partner ID, document types, and protocol. Connection credentials (AS2 URL, SFTP keys, VAN mailbox) are re-established in Epicor EDI or AtlasExchange; partner-specific validation rules are cataloged for rebuild in Epicor's mapping tool. Automotive partners using OFTP2 are configured in Epicor's automotive EDI module with virtual filepaths and certificate exchange completed under Epicor's automotive protocol requirements.

configuration

Connection Protocols → Connection Configuration (Epicor EDI)

Edicom EDI supports AS2, SFTP/FTPS, VAN mailbox, OFTP for automotive, and HTTPS web services.

How it maps

We extract protocol endpoint definitions, credential configurations, and certificate details from Edicom, then re-establish each in Epicor EDI or AtlasExchange by protocol type. AS2 and SFTP credentials (user, password, certificate, URL) transfer as configuration values and are entered manually into Epicor EDI connection settings. VAN mailbox routing tables from Edicom's network are replaced by Epicor EDI's VAN or re-routed via AtlasExchange managed VAN. OFTP2 for automotive requires virtual filepath and certificate setup in Epicor automotive module, which is rebuilt from Edicom's OFTP2 configuration during the mapping phase.

configuration

EDI Mappings → EDI Map Rebuild (Epicor Kinetic / AtlasExchange)

Custom field-level EDI maps in Edicom EDI define how ERP data fields translate into EDI segment positions (e.g., ERP customer part number to X12 N1 segment).

How it maps

Edicom stores maps in a proprietary format; Epicor Kinetic uses its own mapping tool or AtlasExchange map management. We perform a manual field-level inventory of every custom in-house mapping during scoping, output a written map inventory document, and the customer's EDI team rebuilds each map in Epicor Kinetic's mapping interface or AtlasExchange based on our field inventory. Non-standard maps without a clear Epicor equivalent are flagged as requiring re-engineering before cutover.

lookup

ERP Integration Configurations → Epicor Kinetic REST API / Prophet 21 API Integration

Edicom EDI connects to ERP systems (SAP, Oracle, Microsoft Dynamics, NetSuite) via pre-built or custom connectors with field selection, transformation rules, and triggering conditions.

How it maps

We extract ERP integration logic from Edicom configuration exports, then re-implement equivalent integration in Epicor Kinetic using REST API endpoints or in Prophet 21 using its API integration framework. Inbound EDI-to-ERP flows (EDI 850 to Epicor Kinetic Sales Order) and outbound ERP-to-EDI flows (Epicor Kinetic Invoice to EDI 810) are rebuilt as Epicor integration configurations. Epicor's iParts and REST adapter framework replaces the connector logic that was previously managed in Edicom EDI.

1:1

VAN Mailbox Records → AtlasExchange VAN or Epicor EDI Direct Connection

Edicom EDI operates as a Value-Added Network with mailbox addresses per organization and per Trading Partner.

How it maps

VAN routing tables, interchange acknowledgments (997/Contrl), and transmission logs are exported as structured data. We re-establish VAN connectivity in Epicor EDI via AtlasExchange (Epicor's managed VAN) or by configuring direct AS2/SFTP connections for each Trading Partner. Mailbox address assignments and routing configurations are mapped to Epicor's VAN management or AtlasExchange partner routing tables.

What moves14 objects
Edicom EDIEpicor Prophet 21
  • Transaction SetsEDI Document Records1:1
  • Trading PartnersTrading Partner Configuration1:1
  • Connection ProtocolsConnection Configurationtransformed
  • EDI MappingsEDI Map Rebuildtransformed
  • ERP Integration ConfigurationsEpicor Kinetic REST APItransformed
  • VAN Mailbox RecordsAtlasExchange VAN or Epicor EDI Direct Connection1:1

+ 8 more in the mapping below

How Edicom EDI and Epicor Prophet 21 differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionEdicom EDIEpicor Prophet 21
Platform typeStandalone B2B integration layer with multi-standard EDI and managed VANERP platform with native EDI module (AtlasExchange) and ERP-native integration points
EDI standards coverageX12, EDIFACT, UBL, ODETTE, IFTDPC maritime, OFTP2 automotiveX12, EDIFACT, UBL, ODETTE via Epicor EDI; OFTP2 in automotive module
E-invoicingJurisdiction-encoded compliance rules for Brazil, France, Saudi, and 80+ countriesCountry-level mandate support via Epicor Compliance Management; re-implementation required on migration
API accessNo public REST or SOAP API reference; extraction via portal exports onlyEpicor Kinetic REST API and Prophet 21 API for ERP data; EDI API access via AtlasExchange
Trading partner managementPer-partner configuration with individual onboarding and compliance testingAtlasExchange pre-configured templates reduce per-partner onboarding time
ERP integration modelEdicom EDI as separate integration layer with custom ERP connectorsEDI embedded within Epicor ERP; in-house Kinetic or Prophet 21 API replaces EDI middleware
Pricing visibilityNo public pricing; sales-driven contract negotiationEpicor publishes per-tier pricing; AtlasExchange EDI pricing available through Epicor sales

What to watch for in a Edicom EDI to Epicor Prophet 21 migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

No public API reference for Edicom EDI extraction

Edicom EDI does not publish a developer-facing REST or SOAP API reference in its public documentation.

How we handle it

Migration extraction relies on exportable transaction archives, partner configuration files, and EDI mapping documents obtained through the customer portal or direct Edicom support engagement. We request structured data exports (XML/CSV) before planning field-level mapping and flag any configuration retrievable only through Edicom professional services as a potential scope delay. This extraction limitation is specific to Edicom EDI and applies regardless of the destination platform.

high

E-invoicing compliance rules are country-bound and non-portable

Edicom EDI encodes country-specific e-invoicing validation rules, digital signature requirements, and government portal submission flows for Brazil NF-e, France Chorus Pro, Italy SDI, Saudi ZATCA Phase 2, and other jurisdictions.

How we handle it

These rules cannot be exported and loaded into Epicor Compliance Management; each destination jurisdiction requires separate re-implementation with new portal registration and digital certificate issuance. We catalog every active country mandate during discovery, document the Edicom compliance configuration, and itemize the re-implementation effort separately so customers understand that regulatory compliance does not transfer automatically with transaction data.

medium

In-house EDI customizations require manual field-level inventory

Companies with in-house developments on Edicom EDI have often added custom transformations, partner-specific validations, and ERP integration hooks not fully documented in Edicom standard tooling.

How we handle it

These customizations may represent years of accumulated business logic with no external reference. We perform a manual inventory of all non-standard mappings during the scoping phase and flag any map without a clear Epicor equivalent as requiring re-engineering before cutover. The rebuild effort is itemized separately because Epicor's mapping tool or AtlasExchange requires the customer's EDI team to re-implement each map based on our written inventory.

medium

Trading partner re-onboarding requires per-partner compliance testing

Migrating EDI to Epicor ERP requires re-establishing communication with every Trading Partner, re-running compliance testing, re-submitting test documents, and waiting for partner-side acknowledgment.

How we handle it

For companies with dozens or hundreds of active partners, this creates a parallel-run period that extends migration timelines. We coordinate phased cutover by partner tier (top-volume partners first), negotiate test windows with each partner before migrating the full transaction stream, and document the current Edicom compliance testing status as a reference for the re-testing phase in Epicor EDI.

medium

Epicor EDI map structures differ from Edicom mapping format

Edicom EDI and Epicor EDI use different internal formats for field-level mapping configurations.

How we handle it

There is no automated conversion between them. Custom maps from Edicom must be manually rebuilt in Epicor Kinetic's mapping tool or AtlasExchange. We export the complete map inventory from Edicom (input fields, output positions, validation logic, partner-specific rules) as a written document, and the customer's EDI team rebuilds each map in Epicor. We do not rebuild EDI maps as part of standard migration scope; the map inventory document enables the customer's team to complete the rebuild accurately and efficiently.

How the migration runs

  1. Discovery and scope definition

    We audit Edicom EDI across transaction history volume and date range, active Trading Partner count and document types exchanged, EDI standards in use (X12, EDIFACT, UBL, ODETTE), ERP integration points (SAP, Oracle, Dynamics, NetSuite or other), country-specific e-invoicing mandates active in the Edicom platform, and any in-house custom EDI developments.

    What this step covers

    We document every non-standard map, custom transformation, and ERP integration hook. This audit produces the migration scope document, a non-portable mandate itemization, and a custom map inventory requiring rebuild in Epicor Kinetic or AtlasExchange. We also confirm the Epicor edition (Kinetic Cloud, Prophet 21, or BisTrack) and the EDI layer choice (Epicor EDI native, AtlasExchange managed, or hybrid) during this phase.

  2. EDI map inventory and Epicor EDI configuration planning

    We inventory every non-standard EDI map from Edicom EDI at the field level, documenting input fields, EDI segment positions, transformation logic, and partner-specific rules.

    What this step covers

    Each map is assessed for Epicor EDI or AtlasExchange equivalence. Maps with a native Epicor equivalent are marked for configuration migration; maps without a clear Epicor equivalent are flagged for rebuild and included in the written map inventory document delivered to the customer's EDI team. ERP integration configurations (field selection, transformation rules, triggering conditions) are documented for rebuild as Epicor Kinetic REST API integrations or Prophet 21 API integrations. Country compliance rules and e-invoicing mandates are cataloged for re-implementation planning.

  3. Transaction history extraction and Epicor staging migration

    We extract transaction history from Edicom EDI as structured export (XML/CSV) covering all active transaction types and the agreed historical date range.

    What this step covers

    Each transaction record is validated for completeness (document number, date, Trading Partner ID, line items, amounts, status) before transformation. We map Edicom transaction fields to Epicor Kinetic or Prophet 21 order, invoice, and ASN record structures using the Epicor REST API or data import tools. VAN interchange control numbers, acknowledgment status, and functional acknowledgment records are preserved as reference fields. A reconciliation report comparing source record counts and totals against Epicor staged record counts is produced before final load.

  4. ERP integration re-implementation and connectivity validation

    We re-implement ERP integration logic from Edicom EDI as Epicor Kinetic REST API configurations or Prophet 21 API integration points.

    What this step covers

    Inbound EDI-to-ERP flows (EDI 850 purchase orders from Trading Partners into Epicor Kinetic Sales Order records) and outbound ERP-to-EDI flows (Epicor Kinetic invoices into EDI 810 format for Trading Partner transmission) are configured in Epicor's integration framework. We validate that Epicor API credentials, endpoint URLs, and field mappings produce correct ERP records before connecting live Trading Partner traffic. Any custom ERP connector logic from Edicom is documented for rebuild in Epicor iParts or REST adapter.

  5. Sandbox validation and Trading Partner compliance testing coordination

    We run a full migration into Epicor Kinetic or Prophet 21 sandbox environment using production-like data volume.

    What this step covers

    We validate record counts, data integrity, and mapping accuracy against the Edicom source. The customer's EDI team spot-checks 25-50 transaction records for field-level accuracy. Any mapping corrections are documented and applied before production migration. Simultaneously, we begin coordinating compliance testing with Trading Partners in Epicor EDI, establishing AS2, SFTP, VAN, or OFTP2 connections per partner and initiating test document exchange. Top-volume partners complete compliance testing first; lower-volume partners follow in subsequent waves.

  6. Production migration, Trading Partner cutover, and handoff

    We run the production migration in dependency order, then freeze Edicom EDI writes during cutover and migrate any records modified during the migration window.

    What this step covers

    Trading Partner cutover proceeds by tier: top-volume partners migrate first with parallel-run validation (Edicom and Epicor EDI both active, outputs compared per partner), followed by full cutover once trading partners confirm accurate receipt and acknowledgment. We deliver the written map inventory and integration rule document to the customer's EDI team for rebuild in Epicor Kinetic or AtlasExchange. We support a one-week hypercare window for reconciliation issues. Post-migration admin, Workflow rebuild, and EDI map rebuild in Epicor are outside standard migration scope.

Edicom EDI Epicor Prophet 21
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Epicor Prophet 21Rollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

8-10 weeksTypical, smaller accounts
14-18 weeksLarge or heavily customised accounts

This migration sits above CRM-tier pricing because EDI transaction mapping is multi-standard (X12, EDIFACT, UBL), ERP integration requires document-transform logic re-implementation in Epicor Kinetic or Prophet 21, and each Trading Partner needs re-onboarding with compliance testing. Epicor EDI subscription costs (AtlasExchange or Kinetic EDI module licensing) are separate from migration fees and vary by transaction volume and partner count. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Edicom EDI to Epicor Prophet 21 →

Why teams move from Edicom EDI to Epicor Prophet 21

  • Companies running Edicom EDI alongside a separate ERP maintain a two-vendor stack that introduces coordination overhead, extra license costs, and a middleware failure point between B2B document exchange and ERP business logic. Epicor Kinetic and Prophet 21 embed EDI directly, which aligns trading partner communication with order-to-cash and procure-to-pay processes inside the ERP. Reviewers on SelectHub and G2 cite eliminating the standalone EDI layer as the primary driver for migrating to Epicor EDI.
  • Epicor acquired 1 EDI Source in 2024, creating a unified EDI offering purpose-built for Epicor ERP customers. 1 EDI Source provides pre-configured maps, managed EDI services, and a single contract covering both ERP and EDI, replacing the need to maintain a separate Edicom EDI contract alongside an Epicor ERP subscription. Companies cite the unified vendor relationship and reduced procurement complexity as a migration driver.
  • Edicom EDI implementation timelines of 4-8 weeks with ERP integration and 6+ months for greenfield ERP plus EDI setups contrast with Epicor EDI's pre-configured partner templates and AtlasExchange managed onboarding. Orderful's integration guide notes that pre-configured partner templates reduce onboarding from weeks to days, and Epicor EDI's native Kinetic and Prophet 21 integration reduces the ERP connector work that Edicom EDI requires for custom ERP hookups.
  • Mid-market and growing manufacturers consolidate vendor relationships by moving from Edicom EDI (B2B integration layer) plus a separate ERP onto Epicor ERP with built-in EDI. This eliminates two separate renewal negotiations, two support contracts, and the coordination overhead of managing EDI-to-ERP integration as a separate workstream. Industry evaluations on Top10ERP.org and PCMag note Epicor's strength in multi-company, multi-currency, and multi-language manufacturing environments where consolidation reduces total cost of ownership.
  • Epicor Kinetic includes cognitive ERP features (real-time business intelligence, predictive analytics, built-in collaboration) that companies running Edicom EDI as a standalone B2B layer cannot access without additional BI tooling. The end-of-life messaging for on-premise Kinetic, Prophet 21, and BisTrack development in late 2024 accelerated cloud ERP adoption and created urgency to migrate EDI workloads onto a modern Epicor cloud deployment where EDI and ERP share a single operational environment.

Questions, answered

Edicom EDI to Epicor Prophet 21 migration questions

How long does an Edicom EDI to Epicor ERP migration take?

Straightforward migrations with 50-200 Trading Partners, a single EDI standard (X12 or EDIFACT), and no multi-jurisdiction e-invoicing mandates land between 8 and 10 weeks. Complex migrations with hundreds of Trading Partners, automotive OFTP2 protocol requirements, multi-standard environments (X12 plus EDIFACT plus UBL), or multiple active country e-invoicing mandates (Brazil, France, Saudi Arabia) extend to 14-18 weeks because of the trading partner re-onboarding scope, VAN re-establishment per partner, and country-mandate re-implementation planning. Epicor Kinetic or Prophet 21 cloud provisioning timelines run in parallel and are managed as a separate Epicor deployment workstream.

Do Edicom EDI Workflows, Automations, and ERP integration hooks migrate to Epicor ERP?

Edicom EDI processing rules, custom ERP integration connectors, and automation hooks do not migrate to Epicor ERP as executable configurations. Epicor EDI and Edicom EDI use different internal mapping formats with no automated conversion. We deliver a written inventory of every EDI map and ERP integration configuration from Edicom during the discovery phase, documenting input fields, output positions, transformation logic, and partner-specific rules. The customer's EDI team rebuilds each map in Epicor Kinetic's mapping tool or AtlasExchange, and ERP integration logic is re-implemented as Epicor REST API configurations in Prophet 21 or Kinetic. Workflow automation rules requiring rebuild are noted in the handoff inventory for the customer's Epicor administrator.

Do Trading Partners need to be re-onboarded during the migration?

Yes. Every Trading Partner's EDI configuration, compliance test status, and test document history from Edicom EDI does not transfer to Epicor EDI. Each Trading Partner must be re-established in Epicor EDI or AtlasExchange with AS2, SFTP, VAN, or OFTP2 connection credentials, and compliance testing must be re-completed with each partner. We coordinate phased Trading Partner cutover by volume tier: top-volume partners migrate first with parallel-run validation (Edicom and Epicor both active, outputs compared per partner), followed by full cutover for lower-volume partners. We document the current Edicom compliance testing status as a reference for the re-testing phase in Epicor EDI.

What EDI standards does Epicor EDI support compared to Edicom EDI?

Epicor EDI via AtlasExchange natively supports X12 (US retail), UN/EDIFACT (Europe, global logistics), UBL (cross-industry XML), and ODETTE (automotive). OFTP2 for automotive is supported in Epicor's automotive EDI module. Maritime document types (IFTDPC, COPISNL) have limited native support; we assess each active maritime message type during discovery and document whether a middleware approach (iPaaS or direct API integration with the port community system) is needed to maintain maritime document exchange. All standard configurations from Edicom are cataloged and re-created in Epicor EDI by standard type and version, with test credentials and acknowledgment requirements re-established per partner.

What happens to historical EDI transactions like purchase orders and invoices?

Historical EDI transactions from Edicom EDI migrate into Epicor Kinetic or Prophet 21 as production records. We extract the transaction history as structured export (orders, invoices, ASNs, acknowledgments) and load into Epicor ERP order, invoice, and ASN tables using Epicor's data import tools or REST API. Document numbers, dates, line items, amounts, Trading Partner references, and acknowledgment status transfer as structured fields. The compliance testing status and test document history with each Trading Partner does not carry over and requires re-testing in Epicor EDI, which we coordinate by Trading Partner tier during the migration.

Can Epicor EDI handle country-specific e-invoicing mandates?

Epicor Compliance Management supports country-level e-invoicing mandates, but Edicom EDI's jurisdiction-specific configurations (validation rules, digital signature requirements, government portal endpoints, digital certificates) cannot be exported and loaded into Epicor. Each active mandate (Brazil NF-e, France Chorus Pro, Italy SDI, Saudi ZATCA Phase 2, and others) requires separate re-implementation in Epicor Compliance Management with new portal registration and digital certificate issuance. We catalog every active mandate during discovery, document the current Edicom compliance configuration, and deliver a written re-implementation plan as a separate workstream. Re-registration with tax authorities and digital certificate renewal are coordinated by the customer's fiscal or IT team and run in parallel with the data migration.

Does FlitStack AI handle post-migration EDI map rebuild in Epicor Kinetic?

No. The written map inventory document we deliver during migration lists every EDI map from Edicom with its input fields, output positions, transformation logic, and partner-specific rules, enabling the customer's EDI team to rebuild each map accurately in Epicor Kinetic's mapping tool or AtlasExchange. ERP integration re-implementation (inbound EDI-to-ERP flows, outbound ERP-to-EDI flows) is configured by our team as Epicor REST API integrations in Prophet 21 or Kinetic. Country-specific e-invoicing re-implementation is scoped separately as a compliance workstream. Workflow automation, reporting configuration, and dashboard rebuild are outside standard migration scope and can be scoped as separate engagements.

Get a quote

Moving from Edicom EDI to Epicor Prophet 21?

Tell us roughly how many records and objects you have. We scope the mapping and the Epicor Prophet 21 setup with you, then send a quote.

Get a quote