Migrate from weclapp erp to Microsoft Dynamics 365 Business Central

weclapp Customer records map to Dynamics 365 Contact. The customer type field (individual vs company) determines whether a Contact is created standalone or linked to an Account. Address, email, phone, and tax ID fields migrate directly. Tax ID numbers require validation against Dynamics 365 country-specific format rules before insert because Dynamics 365 enforces EU VAT format validation on the Tax ID field in some country configurations.

weclapp Company records (B2B accounts) map to Dynamics 365 Account. Company address and industry classification migrate to Account Address and Industry fields. The Company-Customer link in weclapp requires a two-step migration: the Account is created first as the parent, then the related Contact is linked via the AccountId lookup. weclapp does not support multi-company hierarchies, so all Accounts land in a single business segment unless the customer has manually partitioned data by Company.

weclapp Items (products and services) map to Dynamics 365 Released Products. SKU, description, unit of measure, and cost price migrate to Product Number, Name, Unit of Measure, and Standard Cost respectively. Stock-on-hand figures from weclapp's inventory module migrate to Dynamics 365 inventory dimensions (site, warehouse, location) if the Trade plan inventory module is active. Pricing tiers in weclapp map to Trade Agreements in Dynamics 365, which require configuration of price groups and agreement lines per customer group.

weclapp Sales Orders map to Microsoft Dynamics 365 Sales Order. Customer and Item lookups resolve via the Contact and Product mappings created in earlier phases. Order status (Draft, Confirmed, Delivered, Invoiced) maps to Sales Order Status values, with delivered orders creating corresponding Packing Slips and invoiced orders creating Sales Invoice records. Historical closed orders migrate as completed records.

weclapp Purchase Orders map to Dynamics 365 Purchase Order. Vendor resolution uses the weclapp Supplier records mapped to Vendors in Dynamics 365 Supply Chain. Line items with Item, quantity, and agreed price migrate to Purchase Order Lines. Confirmed and received purchase orders create corresponding Product Receipt records in Dynamics 365.

weclapp Quotes (Sales Quotations) map to Microsoft Dynamics 365 Sales Quote. Validity dates, pricing, and status migrate as Quote Expiration Date, line pricing (via Trade Agreements), and Quote Status. Dynamics 365 requires a Quote to be linked to an Account before insert; we resolve the AccountId at migration time using the Customer-Contact-Account mapping from Phase 1. Expired quotes migrate as read-only records.

weclapp Invoices map to Microsoft Dynamics 365 Sales Invoice. Line items, tax codes, payment terms, and invoice status migrate. Paid and closed invoices in weclapp are immutable and migrate as posted invoices; they should not be reopened or modified in Dynamics 365 to avoid double-posting in financial reports. Dynamics 365 Finance enforces a posted-invoice lock requiring a credit memo for corrections. We flag each reconciled invoice with a custom field migration_flag__c set to closed to alert the customer's finance team.

weclapp Projects map to Dynamics 365 Project Operations projects. The project header (name, status, customer link, start and end dates) migrates as Project. Nested Tasks map to Project Tasks with WBS hierarchy preserved. Time entries attached to tasks migrate as Project Journal Lines. If weclapp Trade plan was active with warehouse-linked projects, the project lines map to Supply Chain integration points that require manual review in Dynamics 365 Project Operations.

weclapp Tasks nested under Projects map to Project Tasks within the corresponding Dynamics 365 Project. Task assignment (User on the source) resolves to the Dynamics 365 Worker or Project Team Member created from the User migration. Task status workflow differs between weclapp editions; we map the closest Dynamics 365 Project Task status value and flag any custom status values requiring administrative reconfiguration.

weclapp Documents attached to Customers, Orders, Invoices, and Projects migrate as files in Dynamics 365 SharePoint integration or as Note attachments linked via the regarding object lookup. We export the binary blobs from weclapp's document storage and re-upload them to the corresponding Account, Contact, Order, or Project record in Dynamics 365. If SharePoint integration is not configured in the destination tenant, we fall back to Note records with file attachments.

weclapp allows custom fields on most standard objects but has no unified custom-field registry. We enumerate custom fields by querying object metadata per-type during discovery and aggregate them into a custom field inventory. Dynamics 365 Finance and Operations requires custom fields to be built as extensions using AL in Visual Studio Code, not added via UI. We provide the complete list of weclapp custom fields with their data types and recommend whether each should become a custom field extension or be absorbed into existing Dynamics 365 fields, with pricing for the AL development scope if required.

weclapp Users map to Dynamics 365 Workers (in Finance and Operations or Project Operations) or Users (in Business Central and CRM). Active user count in weclapp drives licensing costs but does not need to match the destination user count 1:1. We flag deactivated users for exclusion from the active user migration set. Owner assignments on records resolve to the mapped Worker or User by email match during the migration run.

weclapp Helpdesk tickets migrate to Dynamics 365 Cases if the destination tenant includes Service Cloud or Project Service Automation. Ticket status, priority, linked Customer, and agent assignment migrate to Case Status, Priority, Customer (Contact or Account), and Owner respectively. Conversation threads migrate as EmailMessages linked to the Case. This migration only applies to accounts with the weclapp Helpdesk add-on active; we confirm add-on status during discovery and exclude this object if the add-on is not licensed.

weclapp Contract Management records (available on select plans) migrate to Dynamics 365 Project Contracts or Service Management Contracts depending on the destination license. Contract details and linked documents migrate; the contract workflow state (Active, Expired, Renewed) requires administrative reconfiguration in Dynamics 365 because the workflow triggers and renewal automation are platform-specific and do not migrate as code.