Migrate from Streamleader to Microsoft Dynamics 365 Business Central

Streamleader Customer records map to Dynamics 365 Business Central Customer records with direct field translation: customer name, contact details, billing and shipping addresses, payment terms, and tax registration numbers. We flag any Streamleader-specific custom fields discovered during API exploration and map them to Business Central extension fields or custom fields. Customer posting groups are assigned based on the customer's tax status and industry classification extracted during discovery.

Streamleader Vendor records map to Business Central Vendor records with the same direct field translation as Customer: vendor name, contact info, payment terms, and tax IDs. Vendor-specific metadata (bank details, WHS compliance flags) is mapped to the corresponding Business Central fields. We validate vendor codes against the destination's number series configuration.

Streamleader Items map to Business Central Items with SKU, description, unit of measure, cost, and price preserved. Inventory items carry stock-keeping unit data; service items carry service billing information. We flag Streamleader pricing tiers and customer-specific pricing as Business Central Sales Prices entries attached to the Item. Assembly and manufacturing items require additional configuration if Streamleader used these modules.

Streamleader chart of accounts structures map to Business Central G/L Accounts with full hierarchy preservation. Account type (Posting, Heading, Total, Begin-Total, End-Total) and account categories migrate. We flag any custom account segments that require Business Central dimension configuration to maintain reporting continuity. Dimension mapping (Cost Center, Department) is scoped during discovery and configured before account migration.

Open Streamleader AP records (unpaid bills and purchase invoices) map to Business Central Vendor Ledger Entries with current balance, due date, and line items preserved. Partial payments and credit memos are handled as separate ledger entries. We validate that the destination Vendor record exists before AP migration to satisfy the Vendor Ledger Entry's Vendor No. required field.

Open Streamleader AR records (unpaid invoices and credit memos) map to Business Central Customer Ledger Entries with current balance, due date, and line items preserved. Payment terms and discount structures carry forward. The destination Customer record must exist and be validated before AR migration.

Historical transaction migration depends on Streamleader's export API pagination and retention policy. We chunk exports by date range (typically quarterly) to manage API response size and validate line-item counts against source totals. Full audit trail transfer is scoped on a case-by-case basis; organizations requiring complete historical G/L entries budget additional time for multi-quarter extraction and Business Central posting date configuration.

Streamleader user accounts map to Dynamics 365 User records. We export user name, email, and role assignments, but destination permission structures require manual review in Business Central because ERP permission models vary significantly between platforms. Active users are provisioned in the destination tenant; inactive Streamleader users are held in a reconciliation queue for the customer's admin to assign license types before production migration.

Streamleader document blobs (invoices, contracts, receipts) are not confirmed accessible via API given the platform's undocumented attachment surface. We attempt API-based attachment discovery during the technical audit phase. If binary document access is unavailable, we document the file locations for manual transfer to Business Central's SharePoint-connected document management or a separate file migration. This gap is escalated during scoping and reflected in the migration estimate.

Streamleader custom fields are discovered during API exploration because no public schema documentation exists. We map each discovered custom field to a Business Central Table Extension field with the matching data type (Text, Integer, Decimal, Boolean, Option). Custom field dependencies (validation rules, lookup relationships) are flagged and resolved before migration. The absence of source documentation means we cannot guarantee full custom field discovery until live API access is available.

Australian tax codes (GST, BAS categories) from Streamleader map to Business Central Tax Setup entries. We extract tax group mappings and applicable accounts during discovery and configure the destination tax setup before any transaction migration. Australian GST compliance requires correct tax jurisdiction configuration in Business Central's Tax Settings.

Streamleader workflows and automations are not documented in any public API reference. If Streamleader exposes workflow definitions via its API, we export them as a written workflow inventory for the customer's Dynamics 365 admin to rebuild in Business Central Workflow or Power Automate. Workflow code migration is out of scope; we do not translate Streamleader workflow logic into Business Central workflow steps without confirmed API access and schema documentation.