Migrate from Selly Erp to Epicor Prophet 21

Selly ERP Leads map to Epicor Kinetic Prospect records. The Prospect table (UD08) stores pre-customer prospects with fields for company name, contact name, email, phone, and source. We carry over lead source and any custom fields as UD columns on Prospect. The Epicor Kinetic REST API endpoint /api/v1/Prospect handles ingest. Prospects without a company association store contact details in the ShipTo address fields.

Selly ERP Customer records map directly to Epicor Kinetic Customer records in the Customer table (Customer table, not a CRM contact object). Fields mapped include Company, CustID, Name, Address, City, State, Country, PostalCode, PhoneNum, EmailAddress, and TerritoryID. We preserve the Selly billing address as the primary Customer address and any shipping addresses as ShipTo records linked by CustNum. Epicor Kinetic supports multiple ShipTo records per Customer, which covers customers with multiple delivery locations.

Selly ERP Opportunities with an estimated value and close date map to Epicor Kinetic Quote records. The Quote header stores the customer reference, order total, and stage. Epicor Kinetic uses QuoteNum as the primary key and stores line items (PartNum, SellingQuantity, UnitPrice, DiscountPercent) in QuoteDtl. We map the Selly pipeline stage name to the Epicor Quote.QuoteStatus field and carry over the estimated value as the Quote.DocTotal field. Open quotes migrate as active Epicor quotes; closed-won quotes migrate as historical records or convert to Sales Orders if the customer chooses.

Selly ERP Deals that have reached a closed-won state map to Epicor Kinetic Sales Orders. We create OrderHed records with CustomerNum, OrderNum, PONumber, and OrderDate, then create OrderDtl line items from the deal line items with PartNum, Quantity, UnitPrice, and Discount. The Selly deal owner becomes the Epicor BuyerID on the OrderHed. OrderRel (fulfilment release) records are created for each line item based on the requested delivery date.

Selly ERP pipeline stage names (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) map to Epicor Kinetic Quote.QuoteStatus values or a custom Quote Stage UD column if the customer uses Epicor's stage tracking. We extract the full Selly pipeline stage list during scoping, confirm the mapping with the customer, and configure the matching Quote status values in Epicor before migration begins. Stage probability percentages are stored as UD fields on the Quote.

Selly ERP Products map to Epicor Kinetic Part records. The Part table stores PartNum, PartDescription, UnitOfMeasure, TypeCode (stocked, make-to-order, phantom), and CostData. The Selly SKU maps to Part.PartNum, and any Selly product categories map to Part.ClassID or a UD field. Standard cost from Selly migrates as Part.StandardCost. We create PartPlant records for each Epicor site where the part is stocked.

Selly ERP Quote line items map to Epicor Kinetic QuoteDtl records. Each line carries the PartNum (or a description-only line), SellingQuantity, UnitPrice, DiscountPercent, and a reference to the parent QuoteNum. QuoteDtl.DocUnitPrice preserves the original quoted price. If Selly stores pricing by volume break, we create multiple QuoteDtl lines or use Epicor's Quantity Price Break functionality.

Selly ERP Invoices cannot be migrated as structured Epicor ERP transactional records because Selly does not export invoice PDFs as structured data reliably. We archive the invoice PDF files separately and link them to the corresponding Epicor Customer record as a document attachment. The invoice line items (PartNum, Quantity, UnitPrice) are re-imported as structured records manually or via a separate line-item import batch. Customers requiring full invoice history in Epicor should plan for a separate AR import using Epicor's AR Invoice entry or a bulk import tool.

Selly ERP Activities (calls, emails, meetings, tasks, notes) attached to Contacts, Companies, or Deals map to Epicor Kinetic Document records linked via the DocType and Key fields. Activity timestamps migrate as the Document.CreateDate and Document.CreateTime. Email body content stores as Document[1] character data. Meeting location and duration store as UD fields. We normalise timestamps to UTC before Epicor ingest. The activity owner maps to an Epicor User ID for assignment tracking.

Selly ERP custom fields on any object migrate to Epicor Kinetic User-Defined (UD) columns. Each Selly custom field is assessed for data type (string, number, date, boolean, picklist) and mapped to the corresponding Epicor UD data type (string, int, date, boolean, character). We pre-create UD columns in Epicor during the schema phase before any data import. Epicor Kinetic UD columns are created in the Ice.BO.UserFile tables (UD01, UD02, etc.) and linked to the base table via Key1, Key2, Key3 values. Epicor community posts confirm that UD column mapping requires BPM logic for calculated or conditional values.

Selly ERP user accounts map to Epicor Kinetic User records. We resolve owners by email match against the Epicor Kinetic User table. Any Selly Owner without a matching Epicor User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or archived Selly users are migrated as inactive Epicor User records for audit completeness.

File attachments linked to Selly ERP records are extracted from the export and uploaded to Epicor Kinetic's Document Management system. We link documents to the parent record (Customer, Quote, Order, Part) using the DocumentKey fields. Document Type (PDF, image, spreadsheet) is preserved. Attachments that do not survive the bulk export cleanly are stored in a managed file share and linked manually post-migration.