Migrate from EF Enterprise to Infor CloudSuite Corporate

EF Enterprise Exhibitions (event name, dates, venue, status) map to Infor Cloudsuite Industrial Projects using the FSP (Financials Supply Chain Production) module. Each Exhibition becomes a Project header with start/end dates from the EF Enterprise dates, venue name in a custom Project description field, and Exhibition status (Active, Archived, Cancelled) mapped to a custom Project status picklist. Multi-day exhibitions with concurrent tracks are split into separate Project tasks within the Project hierarchy. The Project ID is generated from the EF Enterprise Exhibition ID with a prefix for traceability.

EF Enterprise Booth records (booth number, size, zone, per-booth pricing) map to Project Cost Lines within the parent Exhibition Project using the Project module's cost reporting structure. Booth size in square feet migrates as a quantity field on the cost line; zone assignment migrates as a location reference in the Warehouse Management module (WMS) if the Infor destination includes WMS. Booth pricing from custom EF Enterprise fields migrates as a cost amount on the Project Cost Line. Each Booth retains its Exhibition parent reference via the Project-Phase linkage.

EF Enterprise Sponsors map to Infor Cloudsuite Business Partners. Gold, Silver, Bronze tier flags from EF Enterprise custom fields migrate as a custom Business Partner classification attribute. Sponsors with booth assignments retain that relationship via a Project reference on the Business Partner (mapped through the BP-Project link if available in the destination edition). If the Sponsor is also a paying customer for registration revenue, they are provisioned as both Supplier and Customer BP types. Contact records for sponsor representatives map to the BP's Contact sub-records.

EF Enterprise Attendee Registrations (contact reference, session selections, badge type) map to Infor Contacts with a link to the parent Exhibition Project via Project Resources. Session selections migrate as resource bookings against the Exhibition Project. Badge type migrates as a custom Contact or Project Resource field. Early-bird pricing flags from EF Enterprise custom fields are recorded as custom price modifiers on the Project Resource. If the destination Infor edition lacks Project Resources, registrations are stored in a custom object registered in Infor Data Catalog with identifier, timestamp, and delete-indicator paths explicitly defined per Infor's schema registration requirements.

EF Enterprise Sessions (capacity limits, track classifications, Exhibition association) map to Project Tasks within the parent Exhibition Project. Capacity limits migrate as task quantity constraints. Track classifications (keynote, breakout, workshop) migrate as task type or custom task attributes. Multi-track sessions that run concurrently are split into individual Project Tasks under a parent task representing the overall session block. If the destination Infor edition does not support the required task structure, sessions are registered as a custom object in Infor Data Catalog.

EF Enterprise Badge Records (attendee type, access levels, printing status) map to Project Documents or a custom object registered in Infor Data Catalog. Badge type and access level migrate as document attributes. We disable any Infor document-triggered printing workflows during migration load to prevent duplicate badge generation at cutover, mirroring the approach used for EF Enterprise badge-print triggers. Post-migration, badge printing is re-enabled as a manual verification step.

EF Enterprise extends Salesforce with custom fields for exhibitor contract terms, sponsor ROI tracking, and booth pricing tiers. These custom fields are not discoverable via the standard Salesforce API without a schema export from the source org. We request the Salesforce schema export during discovery, validate every custom field against EF Enterprise's data, and recreate them as Infor custom fields on the appropriate Business Partner, Project, or Project Cost Line object. Fields that cannot map to standard Infor objects are registered as attributes in Infor Data Catalog with explicit identifier, timestamp, and delete-indicator JSON paths per Infor's custom schema registration workflow.

EF Enterprise Owner IDs (Salesforce User records) are remapped to Infor Users using an email-match lookup table built during discovery. Inactive EF Enterprise users (archived rather than deleted per Salesforce convention) are flagged for reassignment to a designated migration User. If Infor Users are not yet provisioned in the destination tenant, Owner references are held in a reconciliation queue and resolved before any record import that requires Owner assignment on Business Partners or Project resources.

EF Enterprise attachments linked to Exhibitions, Booths, and Sponsors migrate as Infor IDM (Infor Document Management) records linked to the corresponding Business Partner or Project. Floor plan PDFs and exhibitor contract documents are chunked and uploaded via Infor ION Document Exchange. Large files exceeding Infor's document size limits are migrated to the Infor Data Lake with metadata pointing to the parent Project, and a document reference is created in IDM for discoverability.

EF Enterprise uses Salesforce standard tags and custom property sets for exhibitor classification. The full tag taxonomy is exported during discovery, deduplicated, and recreated as Infor custom picklist values on the relevant Business Partner or Project object. Tags used for reporting filters are registered as attributes in Infor Data Catalog and tagged on the corresponding Data Catalog objects for cross-object querying alongside financial and operational data.