Migrate from Scopevisio to Epicor Prophet 21

Scopevisio Customer master data (address, communication fields, classification) maps to Epicor Customer records with the Party record as the parent entity. We resolve the Scopevisio customer number to Epicor CustNum and generate the corresponding DcdUserID for the Party. Multi-company Scopevisio configurations export each company's customer ledger separately; we sequence each company's export and link it to the correct Epicor Company in a multi-company Epicor deployment.

Scopevisio Vendor master data mirrors Customer master data structure and maps to Epicor Vendor records. Address, payment terms, and banking details migrate as-is. Global vendors shared across Scopevisio companies are extracted once and linked to each company's vendor ledger to avoid duplication. Epicor's Vendor bank account maintenance records are created from Scopevisio's payment details.

Scopevisio's hierarchical chart of accounts with German SKR types and tax codes maps to Epicor GL Account segments. We extract the full account structure, map Segments 1-9 to Epicor's segment-enabled account mask, and preserve the account description and active/inactive status. German tax codes map to Epicor Tax Types and Tax Codes. If Scopevisio uses a non-standard segment count, we configure Epicor's account mask to match before import.

Scopevisio outgoing invoices with line items, tax, and payment metadata map to Epicor AR Invoice Header and Detail records. Invoice status (open, paid, credit note) migrates separately from document status. We preserve the Scopevisio invoice number as Epicor Reference, the invoice date as InvoiceDate, and the due date as DueDate. For multi-company Scopevisio deployments, each company's invoice set is assigned to the corresponding Epicor Company.

Scopevisio incoming invoices map to Epicor AP Invoice records. Vendor reference, invoice amount, and tax codes migrate. Epicor AP Invoice requires a VendorNum reference resolved from the Vendor mapping; we resolve this before AP import begins. Open and paid statuses carry forward from Scopevisio's accounts payable tracking.

Scopevisio Projects including hierarchy, billing method, and associated cost centres map to Epicor Project records. Project stage status values map to Epicor Project Phase and WBS (Work Breakdown Structure) elements. We preserve the project code, description, start and end dates, and any billing rate matrices. Custom project fields from Scopevisio migrate to Epicor Project UD fields or Project Phase UD fields depending on whether the field is at project or phase level.

Scopevisio time entries are associated with Projects, Employees, and optionally billing records. We map them to Epicor LaborDtl records linked to the migrated Project and the resolved Employee (via LaborType = P for project time or S for shop floor depending on Epicor configuration). Entry date, hours, and any billable flag migrate. If Scopevisio time entries carry a billing rate, we create Project Billing rate detail records in Epicor.

Scopevisio Items including pricing, unit of measure, and stock-control flags map to Epicor Part records. Item codes become PartNum; descriptions become PartDescription. We flag any BOM structures for Epicor's Part Lot tracking or Revision management configuration. Stock-control flags map to Part.UnitStocking, Part.TrackDimension, and Part.TrackLotNum. Custom pricing tiers from Scopevisio map to Epicor Part.SellingFactor and PricePerCode fields.

Scopevisio item BOM structures migrate to Epicor BOM records with PartNum as the parent and BOMDetail records for each component. We resolve PartNum references for all components from the Item mapping, preserving quantity-per and operation sequence. BOM revision dates map to Epicor revision effective dates. Epicor's BOM approval workflow is noted for rebuild post-migration.

Scopevisio fixed asset records (acquisition cost, depreciation method, location, asset classification) map to Epicor Financial Asset records. Depreciation schedules carry forward to Epicor AssetDep records. Epicor's depreciation method options (straight-line, declining balance, units of production) are mapped from Scopevisio equivalents. Asset classification maps to the Asset Group field in Epicor.

Scopevisio HR and payroll data (organisational hierarchy, effective-dated compensation, PTO balances) does not have a direct Epicor ERP equivalent outside the HCM add-on module. We map Employee records to Epicor EmpBasic (name, address, employee type) if Epicor HCM is licensed. Compensation, PTO, and organisational hierarchy are documented as a separate migration scope; we deliver the Scopevisio HR data as structured export files (CSV/JSON) for the customer's HCM admin to configure in Epicor HCM, Workday, or a third-party payroll system post-migration.

Scopevisio DMS documents linked to business objects (invoices, projects, customers) are exported in their original formats and associated via Epicor's Document GUID and DocType system. We reconstruct the object associations by mapping the Scopevisio document's parent entity reference to the corresponding Epicor record ID. File-type verification and size limits are applied per Epicor's Content Service constraints. Scopevisio's GDPdU archive format requires unpacking before document extraction; see gotchas for GDPdU handling.

Scopevisio custom fields on standard objects (Customer, Vendor, Project, etc.) map to Epicor UD columns (UD01-UD09) or user-defined fieldsets depending on the target table. We discover all Scopevisio custom field definitions during scoping, map field types (date, text, numeric, picklist) to Epicor field types, and pre-create the destination schema in the Epicor Sandbox before data import. Type mismatches are flagged for admin review.

File attachments on Scopevisio objects (invoices, projects, customer records) are exported as binary blobs and imported into Epicor as attachments linked to the corresponding record. We maintain the file name, original upload date, and file size during import. Any attachment exceeding Epicor's size limit is flagged for compression or external storage before migration.

Scopevisio multi-company configurations host separate legal entities under one tenant. We treat each Scopevisio company as a separate export scope and map to the corresponding Epicor Company in a multi-company Epicor deployment. Shared objects (global vendors, global items) are extracted once and linked via Epicor's inter-company transaction setup. Inter-company transaction mapping is delivered as a configuration document for Epicor admin setup.