ERP migration
Field-level mapping, validation, and rollback between weclapp erp and Epicor Prophet 21. We move data and schema; workflows are rebuilt natively in Epicor Prophet 21.
weclapp erp
Source
Epicor Prophet 21
Destination
Compatibility
9 of 12
objects map 1:1 between weclapp erp and Epicor Prophet 21.
Complexity
BStandard
Timeline
8-12 weeks
Overview
Moving from weclapp ERP to Epicor ERP is a cross-functional migration from a DACH-focused SMB all-in-one platform to a manufacturing-first mid-market ERP. weclapp bundles CRM, inventory, and accounting under a single subscription; Epicor separates these domains across specialized modules (Supply Chain, Production, Financials) with deeper shop-floor and MES capabilities suited to job shops, make-to-order, and engineer-to-order operations. We preserve Customer, Company, Sales Order, Purchase Order, Quote, Invoice, Item, and Project hierarchies during migration, with particular attention to CSV preprocessing for weclapp exports since Excel silently reformatting date and phone columns is a known source of data corruption. We do not migrate workflows, automations, or DATEV connector configurations; these require re-build at the destination by the customer's Epicor administrator. Manufacturing data (BOMs, work orders, routings) is mapped as part of the Item and Project phases when the source account uses weclapp Trade or Services tiers.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a weclapp erp object lands in Epicor Prophet 21, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
weclapp erp
Customer
Epicor Prophet 21
Customer and ShipTo
1:1weclapp Customers map to Epicor Customer with a one-to-many relationship to ShipTo addresses. The weclapp address block (street, city, postal code, country) splits into Epicor's address fields (Address1, Address2, City, State, Zip). Tax ID from weclapp maps to Customer.TaxRegionCode for US customers or the equivalent VAT field for EMEA. Customer status (active/inactive) maps to Customer.Inactive to prevent importing deprecated records as active.
weclapp erp
Company
Epicor Prophet 21
Customer
1:1weclapp Company records (B2B accounts distinct from individual contacts) map to Epicor Customer. If weclapp stores both individual and company-level records for the same entity, we merge them into a single Epicor Customer with the individual contact stored as a primary ShipTo or linked via CustomerBDContact. We flag duplicate Customer creation during reconciliation.
weclapp erp
Sales Order
Epicor Prophet 21
SalesOrderHed and SalesOrderDtl
1:1weclapp Sales Orders map to Epicor SalesOrderHed (header) and SalesOrderDtl (line items). Order status from weclapp (draft, confirmed, shipped, invoiced) maps to Epicor OrderRel.Status, with shipped lines marked as closed. Customer number from the weclapp Customer maps to SalesOrderHed.CustNum via lookup resolution before insert. Line item pricing and quantity transfer directly from weclapp OrderItem.
weclapp erp
Purchase Order
Epicor Prophet 21
POHeader and PODetail
1:1weclapp Purchase Orders map to Epicor POHeader and PODetail. Vendor lookup resolves from the weclapp vendor company record to Epicor Vendor.VendorNum. Line items transfer with quantity, unit cost, and suggested receipt warehouse from weclapp POItem. We flag any purchase orders in a received or closed state as non-modifiable at the destination to preserve accounting integrity.
weclapp erp
Quote
Epicor Prophet 21
QuoteHed and QuoteDtl
1:1weclapp Quotes map to Epicor QuoteHed and QuoteDtl. Validity dates from weclapp map to QuoteHed.DueDate and a calculated expiration field. Quote status (open, accepted, lost) maps to QuoteHed.QuoteStatus. If the destination Epicor environment uses CPQ (Configure, Price, Quote) as a separate module, we map quotes to CPQ Quote objects instead and flag this decision during scoping.
weclapp erp
Invoice
Epicor Prophet 21
InvoiceHed and InvoiceDtl
1:1weclapp Invoices map to Epicor InvoiceHed and InvoiceDtl. Paid and closed invoices from weclapp import as read-only or locked records in Epicor per standard accounting integrity rules; we flag any records that should not be re-activated to prevent inadvertent re-opening and double-posting. Tax codes require re-creation or mapping to Epicor's tax region configuration after migration.
weclapp erp
Item
Epicor Prophet 21
Part and PartBin
1:1weclapp Items (products and services with SKU, description, unit price, and stock quantity) map to Epicor Part. For weclapp Trade tier accounts, stock-on-hand quantities map to PartBin entries by warehouse. Multiple weclapp pricing tiers per item require separate Epicor Price List records or volume-based breaks mapped to Part.CostID and PriceLst tables. We flag any Item records with zero stock as inactive parts.
weclapp erp
Project
Epicor Prophet 21
Project, ProjPhase, and PjTask
1:1weclapp Projects with nested Tasks and optional time entries map to Epicor Project, ProjPhase, and PjTask. Project status workflow from weclapp (Services vs Trade edition variation) maps to Epicor Project.Phase, with the project header carrying the original weclapp project name and number. Time entries map to Epicor LaborDtl if the destination Epicor environment includes Project Billing or Time and Expense modules; otherwise they map as read-only ProjectLabor records.
weclapp erp
Document
Epicor Prophet 21
DocumentReference or external storage
lossyweclapp Document attachments linked to Customers, Orders, Invoices, and Projects export as binary blobs. We re-upload them to Epicor using DocumentReference records pointing to the original filename and a storage location. If the destination Epicor environment uses Epicor Data Management or an external DMS connector, we configure that integration during the approach phase and flag the storage decision for customer sign-off.
weclapp erp
Custom Fields
Epicor Prophet 21
User Defined Fields (UDF) or UD columns
lossyweclapp custom fields on standard objects require pre-configuration in Epicor before migration. We enumerate all active custom fields during discovery (no unified registry exists in weclapp, so we query object metadata per type), then create matching UD columns in Epicor before data import. Key-value pairs without Epicor equivalents are flagged as manual re-entry candidates. Epicor User Help Forum discussions (epiusers.help) confirm that UD column creation requires Administrator access and is done per-table.
weclapp erp
User
Epicor Prophet 21
User or Employee
1:1weclapp Users map to Epicor User records by email match. Active user count in weclapp affects licensing but does not need to match Epicor user count 1:1. We exclude deactivated weclapp users from migration and flag them for the customer's Epicor admin to handle during provisioning. Epicor requires explicit User provisioning before any Owner references on records can be resolved.
weclapp erp
Helpdesk Ticket (Add-on)
Epicor Prophet 21
Case
lossyweclapp Helpdesk tickets (available only on accounts with the Helpdesk add-on activated) map to Epicor Case if the destination environment includes Service Connect. Ticket status, priority, linked Customer, and conversation threads transfer to Case records. Agent assignments from weclapp map to Epicor Case.Vendor or Case.Owner by email resolution. We confirm Helpdesk add-on activation during scoping; if absent, we warn the customer and exclude ticket records from migration scope.
| weclapp erp | Epicor Prophet 21 | Compatibility | |
|---|---|---|---|
| Customer | Customer and ShipTo1:1 | Fully supported | |
| Company | Customer1:1 | Fully supported | |
| Sales Order | SalesOrderHed and SalesOrderDtl1:1 | Fully supported | |
| Purchase Order | POHeader and PODetail1:1 | Fully supported | |
| Quote | QuoteHed and QuoteDtl1:1 | Fully supported | |
| Invoice | InvoiceHed and InvoiceDtl1:1 | Fully supported | |
| Item | Part and PartBin1:1 | Fully supported | |
| Project | Project, ProjPhase, and PjTask1:1 | Fully supported | |
| Document | DocumentReference or external storagelossy | Fully supported | |
| Custom Fields | User Defined Fields (UDF) or UD columnslossy | Mapping required | |
| User | User or Employee1:1 | Fully supported | |
| Helpdesk Ticket (Add-on) | Caselossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
weclapp erp gotchas
Excel reformatting corrupts CSV import templates
Add-on modules gate Helpdesk and Contract data
No published API rate limits creates planning uncertainty
Custom fields lack a discovery endpoint
Invoice historical records are immutable after export
Epicor Prophet 21 gotchas
Third-party bolt-on integrations complicate migration scope
Dirty data without standardized processes compounds migration risk
SDK customizations and BPMs may not survive platform upgrades
Report-based export only for non-technical users
Per-user pricing model requires accurate user count before migration planning
Pair-specific challenges
Migration approach
Discovery and plan-tier audit
We audit the source weclapp account across plan tier (Starter/Services/Trade), active add-ons (Helpdesk, Contract Management), object-level record counts, custom field inventory per object type, and the presence of manufacturing data (BOMs, work orders, routings). We pair this with an Epicor edition assessment: Epicor ERP for cloud (Kinetic) or on-premises; Prophet 21 if the customer is primarily distribution rather than manufacturing. The discovery output is a written migration scope, a data volume estimate, and a plan-tier gap report for any add-on-gated objects.
CSV preprocessing and format-free extraction
All weclapp CSV exports are opened format-free before any processing. We use the platform's published export method or a text editor to avoid Excel column reformatting. We validate column integrity across all exported objects, flag any records with malformed dates or phone numbers, and correct them before ingestion design. This step is mandatory and precedes all downstream mapping work.
Epicor BAQ and schema pre-configuration
For Epicor Kinetic destinations, we work with the customer's Epicor administrator to configure BAQ-based data sets for Customer, SalesOrder, POHeader, QuoteHed, InvoiceHed, Part, and Project. User Defined Fields are created for each weclapp custom field before data import begins. For on-premises Epicor, we validate direct DB write access and prepare staging tables. Schema is validated in a non-production Epicor environment before production migration begins.
Sandbox migration and reconciliation
We run a full migration into an Epicor test or sandbox environment using production-like data volume. The customer's Epicor administrator reconciles record counts (Customers in, Sales Orders in, Items in, Projects in), spot-checks 25-50 records per object against the weclapp source, and validates BOM and routing data where applicable. Any mapping corrections, field-length truncations, or data-type mismatches are resolved here. This step gates production migration.
Production migration in dependency order
We run production migration in record-dependency order: Customers and ShipTo (parent records), Parts and Price Lists, Purchase Orders, Sales Orders, Quotes, Invoices, Projects and Tasks, Documents (via DocumentReference), Activity history if applicable, then Custom Fields. Each phase emits a row-count reconciliation report before the next phase begins. Epicor Kinetic REST API calls use batch chunking with retry-backoff on rate-limit responses. On-premises Epicor uses direct DB insert with referential integrity checks.
Cutover, validation, and configuration handoff
We freeze weclapp writes during cutover, run a final delta migration of any records modified during the migration window, then enable Epicor as the system of record. We deliver a written inventory of DATEV configuration steps for the customer's accounting team to rebuild in Epicor, a BOM reconstruction guide for manufacturing accounts, and a Helpdesk-to-Case mapping summary if the Helpdesk add-on was active. We do not rebuild weclapp workflows or automations in Epicor; these require the customer's Epicor administrator to configure in Kinetic Process or Epicor Workflow Designer post-migration.
Platform deep dives
weclapp erp
Source
Strengths
Weaknesses
Epicor Prophet 21
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across weclapp erp and Epicor Prophet 21.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
weclapp erp: Not publicly documented — weclapp states no fixed rate limits exist but does not publish fair-use caps.
Data volume sensitivity
weclapp erp doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during weclapp erp to Epicor Prophet 21 migration scoping. Not seeing yours? Book a call.
Walk through your weclapp erp to Epicor Prophet 21 migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave weclapp erp
Other ways to arrive at Epicor Prophet 21
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.