Migrate from Dynamics 365 Business Central

Use Microsoft Entra delegated OAuth to discover a Business Central environment and move supported company data through the reversible Migration Center.

Prerequisites

A Microsoft Entra app registration configured by the Zisyl superadmin.

Dynamics 365 Business Central delegated API permission with admin consent.

The callback URL /api/oauth/businesscentral/callback registered on the Zisyl domain.

A licensed Business Central user with access to the source environment and company.

Data coverage

Source records currently supported by the shared migration engine.

Zisyl area	Source records	Migration behavior
People	users, employees	Users are matched by email and invited securely.
CRM	customers, contacts	Customers and contacts use tenant-scoped duplicate resolution.
Projects	projects, projectTasks	Projects are imported before project tasks.
Accounting	accounts, vendors	Chart of accounts and vendors preserve codes and identities.
Receivables	salesInvoices	Invoice headers, dates, tax, totals, status, and remaining balances.
Payables	purchaseInvoices	Vendor bills and outstanding balances for reconciliation.

1. Prepare Microsoft Entra

Add the Business Central delegated permission and callback to the platform app registration.

1Open the Microsoft Entra app registration used by Zisyl.
2Add the Dynamics 365 Business Central delegated API permission and grant tenant admin consent.
3Add the exact Zisyl Business Central callback URI.
4Confirm the client ID, secret, and tenant configuration are enabled in Superadmin OAuth settings.

2. Authorize Business Central

A tenant admin supplies the Entra tenant and environment before authorizing a licensed user.

1Open Admin → Migration Center and choose Business Central.
2Enter the Microsoft Entra tenant ID and Business Central environment name.
3Save, choose Connect Microsoft, and approve delegated access.
4Run Test & discover companies, then choose the source company.

3. Select and map data

Choose supported Business Central resources and adjust mappings for customized APIs.

1Select users, employees, customers, contacts, projects, accounts, vendors, invoices, and bills as required.
2Review field mappings for custom extensions.
3Set duplicate policies and a conservative record limit.
4Keep invitations enabled when migrated users should activate Zisyl accounts.

4. Validate through the v2.0 API

The dry run follows OData pagination and records every proposed operation.

1Run the dry run without writing tenant data.
2Review inaccessible optional resources and permission errors.
3Resolve duplicate customers, vendors, projects, and financial documents.
4Repeat validation after changing permissions or mappings.

5. Migrate and reconcile

Process approved records in dependency order with resumable batches and rollback.

1Start the approved run and monitor progress.
2Verify customer/vendor balances, invoice totals, projects, and account codes.
3Invite users to establish new credentials.
4Roll back the migration if reconciliation fails.

Microsoft refresh tokens remain encrypted and server-only.

Passwords, MFA secrets, sessions, and source OAuth tokens are never migrated.

Authentication material never migrates

Passwords, password hashes, MFA secrets, sessions, API keys, and OAuth tokens are excluded. Users are matched by email and invited to establish fresh credentials.

Ready to validate your source?

Open Zisyl