Migrate from Certinia ERP Cloud to Microsoft Dynamics 365 Business Central

Certinia Accounts with Customer type map to Dynamics 365 Customer records of type Organization or Person. The Certinia billing address maps to a Customer address entity with address roles (Invoice, Shipping). Multi-entity assignments on Certinia become Dynamics 365 business registrations and tax registration numbers on the Customer record. We resolve the customer number and payment terms before importing any related invoices to avoid orphaned AR references.

Certinia Contacts map to Dynamics 365 Contact records linked to the corresponding Customer (Account). Email, phone, title, and the Contact's role on any related Opportunity migrate directly. Any custom properties added outside the Certinia managed package migrate as custom fields on the Contact entity in Dataverse.

Certinia Opportunities with PSA extension fields (estimated hours, project start dates) map to Microsoft Dynamics 365 Sales Opportunities. StageName from Certinia maps to the D365 sales process stage; Certinia extension fields for estimated hours become custom fields on Opportunity. OwnerId resolves against the User mapping. Closed-won Opportunities do not automatically create Projects; we flag these for manual Project creation or a Power Automate flow to trigger post-close.

Certinia PSA Project records map to Dynamics 365 Project Operations projects or Business Central Projects depending on the target app. Project status, start and end dates, project manager assignment, and milestone hierarchy migrate. Certinia project milestones migrate as Project Tasks with dependencies captured from the milestone relationship records. Budget records link to the Project as cost/revenue budget lines. Note that resource booking and assignment data requires the destination Project Operations resource management module to be provisioned; we stage this data and flag if the module is not included in the D365 license.

Certinia PSA Assignment records linking Resources to Projects map to Project Operations Project Team Member entries. Booking dates, allocation percentages, and role assignments migrate. Resource skillsets from custom fields on the Certinia Assignment are flagged as custom fields requiring destination extension since D365 uses a separate Resource Skills entity rather than inline skill fields.

Certinia PSA Budget records (rate-based, fixed, expense-only) map to Dynamics 365 Project budget lines with cost type and revenue type区分. Each budget type carries different field sets and we apply type-aware mapping during import. Budget hierarchies linking to Projects are resolved at import time so that the parent Project ID reference is satisfied before budget rows insert.

Certinia Billing Events (from PSA Time & Materials, fixed-fee, or subscription billing) export with header and line items. We map Billing Event headers to D365 sales invoices or free text invoices depending on whether the destination uses Project Operations billing or Business Central invoicing. Line items carry the Billing Rule reference that we preserve as a custom field; custom billing rule configurations require manual review post-migration. AR record migration must occur in the same run to maintain open-invoice integrity.

Certinia invoices generated from Billing Events or contracts export with header and line items. We map invoice headers to D365 Free Text Invoice or Sales Invoice based on the destination billing module. Line items carry item number, quantity, unit price, and tax. Linked payment records and AR entries must migrate in the same run to keep the open-invoice picture intact; we do not import invoices without corresponding AR records for the same customer.

Certinia GL entries with multi-dimensional analysis fields (region, department, project) require Dynamics 365 financial dimension setup before posting. We stage GL entry data, validate that destination dimension sets match the Certinia dimensional structure, and flag any account codes with unmapped dimensions. GL entry migration is typically selective (current fiscal year plus one prior) because Dynamics 365 requires open fiscal periods for posting and historical year data is often archived for reporting rather than imported as live journal lines.

Certinia Financial Management Fixed Asset records map directly to D365 Fixed Assets with depreciation schedules, asset categories, and book values preserved. Fixed asset number, acquisition date, depreciation method, and useful life migrate. Depreciation journal entries require a matching GL setup with the fixed asset posting profile established in D365 before the asset registers post.

Certinia POs and AP records carry vendor assignments and approval workflows. We map open POs to D365 Purchase Orders and vendor records to D365 Vendors. Approval history is not available via Certinia's Salesforce API and cannot be exported; we document this gap and recommend the customer preserve approval records as PDF archives if audit continuity is required.

Certinia SCM product mapping records from the SCM Accounting Connector require migration to SCM Line Type to Product Mapping in Supply Chain Management. Certinia's own migration tool renames Freight and Handling to Freight and Customer Deposit to Deposit; we capture the exact line type values at export time and remap them to the new names at import to preserve reporting continuity and prevent orphaned line-type assignments in D365 Supply Chain.

Certinia Users are standard Salesforce records but PSA extends them with Resource Management attributes (skills, utilization targets, cost rates). The Salesforce User record migrates to a D365 User in Dataverse for authentication and ownership. The PSA Resource attributes (skills, utilization, cost rates) must migrate to D365 Human Resources as Worker records with competency and employment detail, since D365 Project Operations resource management reads from HR rather than a standalone user table.

Custom objects built within the Certinia/FinancialForce managed package are accessible via Salesforce API. We export the custom object schema and data together. For D365 with Dataverse (Finance + Operations or Sales), we reconstruct custom objects as custom tables with the same field names and data types. For Business Central targets, custom objects map to extension tables created via AL code before data import. Lookup relationships to standard objects resolve by matching the referenced record IDs against the destination standard object IDs imported in prior phases.

Certinia's multi-entity architecture assigns each subsidiary or business unit as a separate entity with its own ledger, AR/AP, and billing configuration. We stage entity records first and establish Dynamics 365 Legal Entities with corresponding charts of accounts and financial dimension sets before any ledger entries, invoices, or fixed assets post. This prevents dimensional reference errors at the journal level. Multi-currency configuration must match between Certinia and D365 before currency-restricted records (invoices, POs) import.