Migrate from Scopevisio to Infor CloudSuite Corporate

Each Scopevisio legal entity (company within a multi-company tenant) maps to an Infor Cloudsuite Company or Facility record. We treat each Scopevisio entity as a separate export scope and import it into the corresponding Infor Cloudsuite facility. Shared objects like global vendors or shared G/L accounts are extracted once and linked to each facility during import to prevent duplication. Multi-company Scopevisio tenants without a direct Infor multi-entity equivalent require a facility-mapping design decision during scoping.

Scopevisio Customer master data (address, communication fields, payment terms, classification) maps directly to Infor Cloudsuite Business Partner records with BP Type = Customer. The Scopevisio customer number becomes the Infor BP Code; address and banking details map 1:1. Scopevisio custom fields on Customer migrate to Infor custom fields on Business Partner.

Scopevisio Vendor master data mirrors Customer master data structure and maps to Infor Cloudsuite Business Partner records with BP Type = Supplier. Payment terms, banking details (IBAN, BIC), and classification fields transfer directly. Vendors shared across multiple Scopevisio entities are exported once and linked to each entity's vendor ledger to maintain inter-company payable integrity.

Scopevisio's hierarchical chart of accounts with German SKR types (SKR03, SKR04) and tax codes maps to Infor Cloudsuite G/L Account records. We extract the full account hierarchy, map Scopevisio SKR account types to Infor account groups, and flag any German tax-code fields that require Infor tax parameter configuration before invoice import. Account numbers and descriptions transfer directly; account type (asset, liability, expense, revenue) maps to Infor account category.

Scopevisio outgoing invoices carry line items, tax amounts, payment status, and document references. We map invoice header fields (invoice number, date, due date, total) and line items (description, quantity, unit price, tax code) to Infor Cloudsuite A/R Invoice. Scopevisio's separate invoice status and document status fields are preserved as custom fields. Open invoices migrate with outstanding amounts; paid invoices migrate as posted records with full history.

Scopevisio incoming invoices (vendor invoices) map to Infor Cloudsuite A/P Invoice records. We map vendor reference, invoice date, posting date, line items, and tax codes. Infor requires the corresponding Business Partner (Supplier) to exist before A/P invoices can be imported, so vendor master data loads in the preceding phase. Invoice status (open, paid, disputed) transfers directly.

Scopevisio Projects including hierarchy, billing method, cost centre assignments, and project-stage statuses map directly to Infor Cloudsuite Project records. Custom project fields migrate to Infor custom fields. Scopevisio's project cost tracking and billing method (time and materials, fixed price) map to Infor project type and billing rules. Project hierarchy levels preserve as parent-child relationships in Infor.

Scopevisio Time Entries linked to Projects, employees, and billing records map to Infor Cloudsuite Labor Transaction records associated with the corresponding Project. Entry date, hours, billing rate, and cost centre transfer directly. Infor requires the Project and Employee records to exist before labor transactions can be imported, so time entry import runs after both master-data and project migration phases complete.

Scopevisio documents stored in the DMS/ECM layer export as binary files with their original formats (PDF, Office, images). We reconstruct the Scopevisio object-to-document associations (which document belongs to which customer, vendor, invoice, or project) and create Infor Document Management links to the equivalent Infor business objects. GDPdU archive files are unpacked to separate structured accounting data from embedded document blobs before import. The document folder hierarchy does not migrate as structure; we deliver a document-association map for the customer to reconstruct in Infor IDM.

Scopevisio HR and payroll records including organisational hierarchy, effective-dated compensation, and PTO balances map to Infor Cloudsuite Employee records. We map employee number, name, address, employment status, department, and reporting hierarchy. Infor's HR module must be licensed and configured before employee import; compensation history migrates as effective-dated records in Infor HR. Payroll transactions (payslips) are transactional records that Infor typically handles through its own payroll processing cycle rather than importing historical pay run data.

Scopevisio Items including pricing, unit of measure, and stock-control flags map to Infor Cloudsuite Item master records. Item codes, descriptions, and UOM transfer directly. Infor requires Unit of Measure codes to be defined in the system before Item records can reference them, so UOM codes are loaded as a prerequisite sequence before Item import. Stock-control flags and any custom pricing tiers migrate as Infor Item configuration.

Scopevisio Fixed Asset records include acquisition cost, depreciation method, useful life, and location. We preserve the acquisition date, original cost, accumulated depreciation schedule, and asset classification. Infor Cloudsuite Fixed Asset depreciation methods are configured in the asset book before migration; we flag any Scopevisio depreciation methods that do not have a direct Infor equivalent (straight-line, declining balance, units-of-production) for the customer's finance team to confirm.