Migrate from Clear Enterprise to Microsoft Dynamics 365 Business Central

Clear Enterprise Projects are the primary container and carry custom fields that vary per deployment. We profile the live Project schema during discovery, then provision the equivalent Dynamics 365 Project entity (PSA or Project Operations depending on the licensed module) with matching custom fields added as Dataverse columns before import. Project-phase hierarchies map to the Project Task table. Owner assignment resolves via email match to the Dynamics 365 User table.

Clear Enterprise Tasks belong to Projects and may carry custom fields depending on the implementation. We preserve the parent-Project lookup relationship by resolving the Clear Enterprise project_id to the destination msdyn_projectid at migration time. Any custom task properties map to custom columns on the Project Task entity.

Every Clear Enterprise deployment has a different set of custom object types. We discover all custom object types during schema profiling, then pre-create matching Dataverse custom entities in the destination environment before any data moves. Lookup relationships to standard entities (Contact, Account, Project) are provisioned as Dataverse lookup columns. Many-to-many relationships translate to Dataverse intersect entities.

Clear Enterprise Contacts map directly to Dynamics 365 Contact. Name, email, phone, address, and owner assignment are consistently present and migrate as typed fields. The company_id reference on the Contact record maps to the Account customerid lookup, which we resolve at migration time once Account records exist.

Clear Enterprise Companies (or Accounts) map to Dynamics 365 Account. The company domain or website becomes the Account Website field. We create Account records before Contact import so that the customerid lookup is satisfied at the moment of Contact insert. Address and industry fields translate directly.

Documents attach to Projects, Tasks, and Custom Objects in Clear Enterprise. We export file attachments individually, upload them to the appropriate SharePoint document library attached to the parent Account, Project, or custom entity, and create a SharePointDocumentLocation record in Dataverse linking each file to its parent record. Document metadata (created date, author, tags) migrates as column properties on the SharePoint file.

Clear Enterprise Users map to Dynamics 365 User records by email address match. Role and permission translation requires a per-implementation review because Clear Enterprise role definitions are custom. We produce a role mapping matrix that the customer's Dynamics 365 admin uses to assign the correct Security Role and Field Security Profile post-migration.

Clear Enterprise Teams aggregate Users and may control access scoping. Dynamics 365 Teams map to the Azure Active Directory group membership and the Dataverse Team record. Where Clear Enterprise uses a hierarchical team model, we flatten it into a flat Access Team or Owner Team structure in Dynamics 365, which the customer validates during UAT.

If the Clear Enterprise deployment includes a Chart of Accounts, we map it to the Dynamics 365 Finance MainAccount table. Account number, name, account type, and financial dimension assignments migrate directly. Where Clear Enterprise uses custom account categories, we create a mapping to the Dynamics 365 MainAccountCategory.

GL transaction data migrates with careful attention to currency, tax codes, and effective-dated balances. Each journal entry line maps to the GeneralJournalEntryLine entity with the appropriate MainAccount reference, dimensions, and amount. We validate that effective dates fall within the Dynamics 365 fiscal calendar periods configured in the destination environment before import.

Currency codes from Clear Enterprise map to the Dynamics 365 TransactionCurrency table by ISO 4217 code. Exchange rates migrate as CurrencyLayer or manually entered into the ExchangeRate table, with effective dates preserved. Multi-currency balances convert using the configured exchange rate at the transaction date.

Tax codes from Clear Enterprise map to the appropriate Dynamics 365 tax configuration entity. We create Tax Codes in Dynamics 365 Finance or Tax Groups and Tax Codes in Business Central that match the source configuration, including rate, applicability, and posting definitions. The customer validates tax posting profiles before financial records import.

Any custom properties discovered during schema profiling that do not map to a standard Dynamics 365 field become Dataverse custom columns on the appropriate entity. We use the logical name from Clear Enterprise (sanitized to Dataverse naming conventions) as the column display name, with a schema name of new_<sanitizedname>__c. Picklist values become option sets; multi-select values become multi-select option sets.

All created-on and modified-on timestamps from Clear Enterprise migrate to the corresponding Dynamics 365 system columns (CreatedOn, ModifiedOn) where the destination field supports date preservation. For entities where system columns are immutable, we create custom datetime columns (new_original_created_on__c, new_original_modified_on__c) to preserve the source timestamp for audit and reporting.