Migrate from EF Enterprise to Acumatica

EF Enterprise exhibitors — companies reserving booth space — map directly to Acumatica Customers. The exhibitor name becomes CustomerName; billing address maps to CustomerLocation. Sponsorship tier (Gold, Silver, Bronze) migrates as a custom field (USRSponsorshipTier__c) or Acumatica Customer Class. Original create dates, modification timestamps, and owner assignments are preserved as custom fields (Original_Create_Date__c, Source_System_ID__c) leveraging Acumatica's extensible DAC framework.

Primary and secondary exhibitor contacts migrate to Acumatica Contacts linked to the Customer record. Email, phone, and title map directly. Additional contacts beyond the primary pair are added as Contact Records under the same Customer account. The migration process performs email matching against existing Acumatica Contact records to prevent duplicates, and flags any contacts that do not match for administrative review.

Booth units (10x10, 20x20, island, corner) are modeled as Non-Stock Inventory Items in Acumatica with the Item Class set to BoothType. Booth amenities (electricity, Wi-Fi, furniture) map as separate line items or as attributes on the Non-Stock item using Acumatica's Attribute feature.

Each exhibitor's booth reservation becomes an Acumatica Sales Order or AR Invoice tied to the Customer. The Order Nbr references the original event ID; line items reflect booth type, additional services, and sponsorship add-ons. Historical invoices from past events become Posted AR Invoices with original dates preserved.

Complimentary attendees and session-only registrations merge into Acumatica Contacts under the sponsoring Exhibitor's Customer account. Paid attendee registrations with separate billing become separate Customer records to preserve AR aging for event-wide invoice runs. Registration type and badge print status migrate as custom fields (USRRegistrationType__c, USRBadgePrinted__c) on the Contact record.

Conference sessions and educational tracks map to Acumatica Projects with tasks representing individual sessions. Project Budget Lines capture session costs (venue, speaker, materials). Project Transactions link attendee count and session attendance to the project for ROI reporting. CE/CME session credits migrate as a custom decimal field (USRSessionCredits__c) on the Project Task.

Each trade-show event becomes an Acumatica Project header. Event name, dates, and venue map to ProjectName, StartDate, and a custom venue field (USRVenue). Past events receive Completed or Inactive status; current events become Active. All exhibitor booths, sessions, and registrations under that event link as child records to the Project for comprehensive event tracking.

Sponsorship packages (title sponsor, lunch sponsor, badge sponsor) are modeled as Sales Order lines with a custom field (USRSponsorType__c) marking the sponsorship level. Multiple sponsorship tiers per exhibitor aggregate on the same Order, with separate lines for each tier. Sponsor amounts populate LineAmount for accurate financial reporting and invoice segmentation.

EF Enterprise file attachments — booth layout PDFs, exhibitor logos, badge design templates — re-upload to Acumatica's File Repository linked to the relevant Customer (exhibitor logo), Inventory Item (booth diagram), or Project (event badge template). File size limits per Acumatica upload apply.

EF Enterprise custom properties that have no direct Acumatica equivalent (e.g., sponsorship tier, booth electricity voltage, session credit count) are migrated as Acumatica custom fields prefixed with USR. Your Acumatica admin creates these in the Customization Project before migration lands.

Internal notes left on exhibitor records in EF Enterprise migrate as Acumatica Activities (Note type) attached to the Customer. Original creation timestamps and author names preserved in the Activity's CreatedDateTime and Owner fields. Note authors resolved by email matching against Acumatica Users; any authors without matching email addresses are flagged for manual owner assignment review.

EF Enterprise owner assignments on exhibitors, booths, and sessions resolve by email match against existing Acumatica Users. Unmatched owners are flagged before migration; you either invite them to Acumatica first or assign records to a fallback owner designated by your team.