Migrate from Termene to Microsoft Dynamics 365 Sales

Dynamics 365 Sales Professional caps custom tables at 5—custom fields may require an upgrade

Termene's Romanian registry data includes VAT status, insolvency flags, debt-alert levels, credit scores, risk ratings, and source-registry provenance. Each distinct data point typically requires a custom field on the Account entity. Dynamics 365 Sales Professional (at $65/user/month) limits custom tables to 5 total. If your Termene data includes more than 5 distinct custom properties per record, the migration plan must include an upgrade to Sales Enterprise ($105/user/month) which removes this cap. We identify the exact custom-field count during the sample migration phase and flag the license upgrade requirement before the full run commits.

Romanian company identifiers (CUI/CIF) have no native Dynamics 365 field—custom field required for compliance

Every Romanian legal entity carries a unique CUI (Cod Unic de Identificare) or CIF for VAT purposes. Dynamics 365 Sales has no native field for this identifier—the closest standard fields are TickerSymbol (intended for stock ticker) and AccountNumber (free-form). We store the CUI in TickerSymbol for display convenience but also create a custom text field CompanyId__c on Account to ensure the identifier is searchable, unique-constrained, and available for Romanian regulatory reporting without being confused with a stock ticker. If your team uses CUI for duplicate-detection or API lookups, the CompanyId__c field must be indexed—Dynamics 365 Enterprise allows field indexing; Professional does not by default.

Termene debt alerts map to Tasks, not Account fields—alert fatigue requires inbox rules

Termene surfaces debt alerts as flags on company dossiers; the alert semantics (overdue invoice, bounced payment, registry listing) vary. We map these to Dynamics 365 Tasks attached to the Account with the registry source and amount in the Description. This preserves every alert but means the Account record itself does not change when a new alert arrives post-migration. Your Dynamics 365 admin should configure Power Automate flows or alert-inbox rules to notify owners when a new Task is created on an Account with DebtAlertLevel__c set to 'Alert' or 'Critical', or sales reps will miss time-sensitive alerts buried in the Activity timeline.

Termene's flat dossier model does not map to Dynamics 365's relational Account-Contact-Opportunity graph

Termene stores companies and their representatives in a denormalized dossier structure—a single Termene record may contain multiple contact entries without explicit primary-contact designation. Dynamics 365 Sales requires Contacts to have an AccountId lookup. We establish the AccountId on every Contact record and designate one Contact per Account as IsPrimaryContact__c = true based on the Termene 'administrator' flag or most senior role title. If Termene contains contacts without a clear role hierarchy, all contacts migrate with the same AccountId and no primary designation—your Dynamics 365 admin should review and assign a primary contact manually after migration.

Termene risk scores are proprietary—Dynamics 365 Copilot cannot interpret them without custom training

Termene's composite risk score and letter-grade rating reflect a proprietary algorithm applied to Romanian financial-registry data. Dynamics 365 Sales Copilot AI provides lead-scoring insights based on engagement data and Dataverse fields, but it cannot ingest Termene's risk model natively. We migrate the numeric CreditScore__c and RiskRating__c fields as custom fields on Account, making them visible to sales reps. However, using these fields in Dynamics 365 Copilot scoring models or predictive-forecast rules requires a custom AI model built with Azure Machine Learning or Power Automate logic that references the Termene score ranges—Copilot's built-in scoring does not consume custom fields by default.