Migrate from Scopevisio to Microsoft Dynamics 365 Business Central

Scopevisio customer master data (address, communication fields, classification, payment terms, banking details) maps to D365 Dataverse Account and Contact. We extract the full customer record including any custom fields, then create the Account first (serving as the parent for billing and shipping addresses) before creating the Contact as the primary person-of-contact linked via the accountId lookup. Payment terms and currency map to D365 PaymentTerm and TransactionCurrency respectively.

Scopevisio vendor master data maps to D365 Vendor in Finance and Operations or to Account with vendorRole in Dataverse CRM. The vendor's address, payment terms, and banking details migrate to VendTable in Finance. We preserve the vendor classification from Scopevisio (Lieferantenkategorie) as a Vendor group in D365 that drives default posting profiles.

Scopevisio invoice records (outgoing and incoming) include line items, tax codes, payment status, and document status tracked separately. We split outgoing invoices to CustInvoiceJour and incoming vendor invoices to VendInvoiceJour. Invoice status and document status from Scopevisio map to InvoicePostingProfile and LastInvoiceDate in D365. Open and paid states translate to the D365 LedgerTransOpen table references. GDPdU-embedded invoice PDFs are extracted as separate document files for SharePoint or Dataverse attachment routing.

Scopevisio project records including hierarchy, billing method, cost centres, and project-stage status map to D365 smmProject in CRM contexts or msdyn_project in Project Operations. We preserve project hierarchy as a parent-child project structure, map Scopevisio billing method to D365 project billing method (time and material, fixed price, or cost-only), and carry forward custom project fields as D365 project custom fields. Project contracts migrate as agreements attached to the project.

Scopevisio time entries are associated with projects, employees, and billing records. Each entry carries entry date, hours, and billing flag. We map these to D365 smmProjectTimeUsage or msdyn_timeentry depending on the Project Operations edition activated. Employee reference resolves via the HcmWorker lookup. Non-billable versus billable flag from Scopevisio maps to ProjPostingProfile in D365 for cost posting.

Scopevisio maintains a hierarchical chart of accounts with German SKR-type fields and tax codes. We extract the full account structure and map each Scopevisio account to D365 MainAccount with the account number as the account number, the account name as the name, and the account type (Erfolg, Bestand, RUB) as the D365 account type. German tax codes map to D365 TaxGroup and TaxCode combinations. This is a configuration step that requires customer confirmation of the D365 chart-of-accounts layout before import begins.

Scopevisio items include pricing, unit of measure, item code, and stock-control flags. We map these to D365 EcoResProduct (the unified product entity) and InventTable (the inventory-specific attributes). Item pricing migrates as TradeAgreement records with price groups linked to the customer or vendor. Custom pricing tiers from Scopevisio become D365 PriceDiscTable entries. BOM structures require separate configuration in D365 and are flagged as a rebuild item.

Scopevisio document management is tightly integrated with business objects, meaning each invoice, project, and customer has associated documents in the same DMS tree. We export documents in their original formats (PDF, Office, images) and reconstruct the object associations in D365 by routing to SharePoint document libraries (for Finance and Supply Chain document handling) or Dataverse FileAttachments (for CRM and Project objects). The original Scopevisio document path is preserved as a metadata field for audit continuity. DMS permissions do not migrate and are documented separately for the admin to re-configure.

Scopevisio HR and payroll data includes effective-dated compensation, organisational hierarchy, and PTO balances. We map employee records to HcmWorker, preserving the person name, employment type, department, and position. Payroll statements migrate to PayrollStatement or equivalent payroll tables depending on the D365 Human Resources or third-party payroll add-in in use. Compensation effective dates map to HcmCompensationLevel. Bank account details for payroll direct deposit migrate to DirPartyBankAccount. Scopevisio Organisation-only tier customers without HR module access do not have payroll data to export.

Scopevisio fixed asset records include acquisition cost, depreciation method, asset classification, and location. We map these to D365 AssetTable with AssetGroup, DepreciationMethod, AcquisitionDate, and AcquisitionCost preserved. The depreciation schedule (Nutungsdauer and Abschreibungsmethode) maps to D365 DepreciationMethod and service life in months. Asset status (aktiv, in repair, retired) maps to AssetStatus. Note that D365 handles depreciation posting to the general ledger via AssetBook integration.

Scopevisio multi-company configurations host several legal entities within a single tenant, each with its own chart of accounts, customer ledger, and document store. We treat each Scopevisio entity as a separate export scope, then map to D365 legal entities (Finance and Operations) or companies (Business Central). Shared objects (global vendors, shared items) are extracted once and linked to each legal entity's ledger during import, avoiding duplication. Inter-company transaction records (between-Scopevisio-entity invoices) require the customer to confirm how intercompany transactions should be represented in D365.

Scopevisio multi-currency support stores currency codes, exchange rates, and tax codes per transaction. We map currency codes to D365 Currency, exchange rate types to ExchangeRateType, and Scopevisio tax codes (MwSt satz 19%, 7%, 0%) to D365 TaxCode and TaxGroup combinations. German VAT reporting configurations require manual setup in D365 and are documented as a configuration item rather than migrated data.

Scopevisio custom fields on any standard object are discovered during scoping and mapped to D365 User-Defined Fields in Finance and Operations or custom fields in Dataverse. We handle type differences including date, text, integer, decimal, and picklist variants. Scopevisio picklist values map to D365 picklist values or enumerations. Custom field definitions and data migrate together to avoid orphaned values. If the destination D365 edition does not support the target field type, we flag it for admin review before import.

File attachments on any Scopevisio object export as binary blobs paired with their parent record reference. We migrate each attachment to D365 FileAttachments (stored in Dataverse or Azure Blob) or to SharePoint document libraries depending on the D365 configuration. File-size limits for D365 Dataverse (115 GB per database) are respected by chunking large file sets. Attachment metadata (file name, MIME type, upload date, attached-by user) is preserved as SharePoint column metadata or Dataverse file record attributes.