Migrate from EF Enterprise to Epicor Prophet 21

EF Enterprise Exhibitions (top-level event container with name, dates, venue, status) map to Epicor Job or Project depending on whether the destination Epicor instance has Project module licensed. We use Job as the default since Project requires additional licensing. Exhibition metadata (name, start/end dates, venue) migrates to JobHead fields; custom fields storing exhibition type or classification migrate to UD columns on JobHead. If the customer has multi-year exhibition history, we recommend archiving Exhibitions older than 24 months rather than loading them into Epicor Job, since Epicor Job is optimized for active production rather than historical event records.

EF Enterprise Booth records (booth number, size, zone, per-booth pricing) map to Epicor Job records with JobMtl line entries for booth components. Booth size and zone assignment migrate as JobMtl or UD columns on JobMtl; per-booth pricing migrates to the JobProd cost record linked to the Job. We preserve the Exhibition parent reference as the JobHead.JobNum, and we flag any booth records that reference deprecated sponsors as orphaned and requiring resolution before migration.

EF Enterprise Sponsor records (company name, tier, contact information) map directly to Epicor Customer records. Sponsor tier (Gold, Silver, Bronze) migrates to Customer.Territory or a UD column on Customer if the destination Epicor org uses a territory structure not mapped to standard Customer fields. We use the sponsor company name as the Customer.Name and resolve the CustomerID from the Customer table before any Booth-to-Sponsor linking occurs.

EF Enterprise Booth-Sponsor associations are resolved at migration time by matching the Sponsor CompanyName to the newly created Epicor Customer record and linking that CustomerID to the Job record representing the Booth. Epicor does not have a native booth-sponsor junction object; we represent the relationship as a UD table (e.g., SponsorBoothLink_c) with JobNum and CustNum columns if the customer requires queryable sponsor-booth linkage in Epicor.

EF Enterprise Attendee Registration records (contact reference, session selections, badge type) map to Epicor Contact records linked to the relevant Customer or Job. Session selections migrate as UD columns on Contact or as entries in a session-tracking UD table. Badge type migrates to a UD column on Contact. Attendee contact information (name, email, phone) maps to the standard Epicor Contact fields Name, EMailAddress, and PhoneNum.

EF Enterprise Sessions (linked to Exhibition, with capacity limits and track classification) map to Epicor Job records if the destination uses Jobs for scheduling, or to a custom UD table (Session_c) with fields for Exhibition reference, capacity, track, and status. Multi-track sessions are flattened into individual session records at migration time, with each receiving a track-specific identifier in a UD column.

EF Enterprise Badge Records (attendee type, access level, print status) have no direct Epicor equivalent. We migrate the badge metadata as UD columns on the Contact record (badge_type_c, access_level_c, print_status_c). The badge print workflow does not migrate — we document the original Salesforce Flow or Apex trigger logic in the automation inventory and recommend rebuilding using Epicor BPMs or a third-party badge-printing integration post-migration.

EF Enterprise Owner assignments map to Epicor User records by resolving the Salesforce User email to the Epicor SysUserID. Inactive Salesforce Users (archived rather than deleted per the EF Enterprise pattern) are flagged for reassignment during scoping. Any EF Enterprise Owner without a matching Epicor User goes to the reconciliation queue for the customer's admin to provision before record import resumes.

Attachments linked to EF Enterprise Exhibitions, Booths, Sponsors, and Attendee Registrations migrate via the Epicor Attachments Business Object. We extract the Salesforce ContentDocument (file name, body, content type) and upload to Epicor with the related JobNum or CustNum reference. Large floor plan PDFs are chunked and re-uploaded individually. Attachments are linked to the Job record representing the Exhibition or Booth.

EF Enterprise tag taxonomy (exhibitor classification tags, sponsor tier tags, zone tags) is exported in full and recreated in Epicor as UD column values or entries in a custom classification UD table depending on the cardinality. Duplicate tags are merged at migration time. The customer chooses tag-to-UD strategy during scoping.

EF Enterprise custom objects (exhibitor contracts, floor plans, lead retrieval) have no direct Epicor equivalent and migrate to Epicor UD tables if the customer provides a schema export during discovery. UD table creation (ZDataTable metadata) is deployed to Epicor before data load. Without schema access, custom objects are flagged as unsupported and excluded from the migration scope.

EF Enterprise marks deprecated exhibitor records as inactive rather than deleting them, a Salesforce pattern. We surface the full inactive record list during the discovery review. Inactive Exhibitions, Booths, and Sponsors are migrated as archived records (with a status flag in a UD column) only if the customer requests it; otherwise they are excluded from the migration scope. Archived Attendee Registrations are excluded by default since they represent past events already concluded.