Migrate from iCast to Microsoft Dynamics 365 Business Central

iCast customer records include payment terms, credit limits, account managers, and contact details. We map these to Dynamics 365 Customer records, creating separate Contact records linked to the Customer where iCast stores multiple contacts per account. Custom fields on the iCast customer record are inventoried during discovery and flagged for recreation as Dynamics 365 custom fields before migration; the original field name and data type are preserved in the inventory document.

iCast vendor records include address, payment terms, and account numbers. We map these to Dynamics 365 Vendor records and create linked Contact records where applicable. We audit for duplicate vendor records during load by matching on vendor account number and address combination. Vendor-specific custom fields follow the same inventory and recreation process as customer custom fields.

iCast inventory items include SKU, description, unit of measure, cost, and warehouse location. We handle multi-location inventory by mapping iCast location codes to Dynamics 365 site and warehouse records, which must be configured in the destination before inventory data loads. Unit of measure conversions between iCast UoM definitions and D365 unit of measure groups are resolved during the transformation step. For items with lot or serial number tracking, we map the existing lot numbers to D365 item tracking groups and validate serial number uniqueness during load.

Open and historical sales orders include line items, pricing, quantities, and order status. We map iCast order statuses to Microsoft Dynamics 365 Sales order status values, and preserve the original order number as a reference field. Lines map to Sales Order Lines with item number, quantity, unit price, and discount amount. Orders in a held or pending state require manual review before migration to confirm they should be carried forward; we flag these in a pre-migration status report.

Purchase orders contain vendor references, line items, quantities, expected dates, and terms. We map these to Dynamics 365 Purchase Order records, resolving the vendor account reference at migration time. Line items map with item number, quantity, cost price, and any landed cost allocation. Historical purchase orders that are fully received are migrated as closed records; open POs are migrated with their current status preserved so that the receiving team can continue fulfillment in Dynamics 365.

iCast maintains a hierarchical chart of accounts used for all financial posting. The iCast account structure maps to Dynamics 365 main accounts, where each account carries a type (Revenue, Expense, Asset, Liability, Equity), account group, and optionally a financial dimension framework. We map iCast account numbers and types directly, flagging any accounts that appear in transaction history but do not yet exist in the destination chart. Account dependencies must be resolved before any journal entry migration begins because D365 requires that all account references are valid at posting time.

General journal entries include date, account references, debit and credit amounts, and memo fields. We map journal lines to Dynamics 365 General Journal lines, preserving the original entry date and posting date. Entries with non-standard account mappings (accounts not in the destination chart) are flagged in a pre-migration exception report. Historical journal entries migrate within a scope window agreed with the customer during discovery; deep historical data beyond the scope window can be archived in a read-only SQL database for reference rather than loaded into the operational D365 company.

iCast user accounts include login credentials, roles, and access permissions. We extract user records and map them to Dynamics 365 User accounts by email. Role structures are reviewed during discovery; if iCast uses custom role names or granular permission sets, we document them for the customer's Dynamics 365 administrator to map to D365 security roles and permission sets. Users who are inactive in iCast at migration time are created as inactive D365 users for historical record ownership continuity.

For manufacturing customers, iCast stores production orders, bill of materials, and routing definitions tied to job costing. We map these to Dynamics 365 Finance and Operations Production Order and BOM records (or Business Central Manufacturing if that is the destination tier). BOM lines map to production BOM versions, and open production orders are migrated with their current status and remaining quantities. Routing definitions map to Operations Resources and Routes. Custom job-costing fields are inventoried for recreation as D365 custom fields or cost group assignments.

iCast customers frequently build custom fields across Customers, Vendors, Items, Orders, and journal entries. These have no automatic export path and must be manually inventoried during discovery. We document every custom field's name, data type, the object it belongs to, the data it contains, and its intended business purpose. The inventory document is delivered to the customer's Dynamics 365 administrator as the authoritative reference for recreating each field in the destination system. Custom fields with embedded business logic (calculated fields, conditional defaults) require a separate functional review to determine whether the logic maps to a D365 native feature, a Power Apps formula, or a custom extension.

iCast supports file attachments on records such as sales orders, purchase orders, and inventory items. We migrate these as document attachments in Dynamics 365 using the standard Document Handling or SharePoint integration, depending on the destination configuration. Attachments that reference external URLs in iCast are mapped to external document links in D365. Large attachment volumes (over 10 GB total) require a storage plan before migration to ensure D365 environment storage limits are not exceeded.

iCast multi-location customers store inventory across multiple warehouses or physical sites under a unified database. Dynamics 365 requires Sites and Warehouses to be configured as setup data before inventory records can reference them. We extract all distinct location codes from iCast inventory records, map each to a corresponding D365 site and warehouse combination, and ensure that the location-to-site mapping is validated in the destination environment before the inventory snapshot is loaded. Location-specific stock quantities are preserved per site-warehouse combination.