Migrate from Centerpoint ERP to Microsoft Dynamics 365 Business Central

Centerpoint CRM Contacts map directly to Dynamics 365 Contact records. We extract via flat-file export using the customer's built-in Data Importer, validate email format and phone number normalization, and map Centerpoint owner assignments to Dynamics 365 User records by email match. Any Contact without a resolved User owner enters a reconciliation queue for the customer's admin to assign before production import.

Centerpoint CRM Leads map to Dynamics 365 Lead records. Lead status values from Centerpoint's staged workflow migrate to the Dynamics Lead Status field, with any custom workflow stage names mapped to the customer's configured status picklist values during destination schema setup. We preserve the Centerpoint lead creation date as a custom field for historical reporting.

Centerpoint Opportunities map to Dynamics 365 Opportunity. The deal value, stage name, close date, and owner assignments migrate directly. Centerpoint's weighted and unweighted forecast values require a migration option decision during scoping: we either preserve both as custom fields in Dynamics or map the unweighted value to the standard Amount field depending on the customer's reporting requirements.

Centerpoint Company records from the CRM module map to Dynamics 365 Account. The Company name becomes the Account Name field, and the Company domain or address fields map to the Account address structure. Account is imported before Contacts so that the Account-Contact Lookup is satisfied at the moment of Contact insert. Vendor companies from the Purchasing module may share the same Account record for supplier-customer consolidation scenarios.

Centerpoint Asset Management module assets map to Dynamics 365 Fixed Asset (Business Central Essentials/Premium) or Asset Management entities (Finance & Operations). Current value, depreciation schedule, location, and asset hierarchy migrate directly. We map the Centerpoint depreciation method to the equivalent Dynamics depreciation book configuration. Fixed Asset numbers are assigned sequentially or matched to a customer-defined numbering series during import.

Centerpoint Work Orders map to Dynamics 365 Work Order (Finance & Operations Service Management module) or to Project records with tasks (Business Central). Each Work Order's linked asset, technician assignment, safety prerequisites, and status history migrate as a parent-child set. Work Order line items map to the corresponding service task lines. If the customer does not license the Finance & Operations Service module, Work Order records migrate as Project tasks with a custom status field for admin reference.

Centerpoint HR Employee records map to Dynamics 365 Human Resources Employee. Department and role assignments migrate to the corresponding Dynamics HR legal entity and position structure. Employee records contain PII that requires explicit written customer authorization before extraction. We extract via flat-file from the HR module, apply field-level encryption or redaction per the customer's data handling policy, and map HR organizational units to the Dynamics 365 HR legal entity hierarchy.

Centerpoint Purchasing Purchase Orders map to Dynamics 365 Purchase Order records. Vendor links resolve via the Account mapping, and line-item detail (item number, quantity, unit cost) migrates directly. If Centerpoint stores vendors as separate Vendor records rather than as Company records with a vendor flag, we perform a value-mapping pass to consolidate vendor names and prevent duplicate Accounts in Dynamics.

Centerpoint QHSE records (safety incidents, audits, inspections, compliance logs) have no native Dynamics 365 equivalent object. We review the customer's QHSE configuration during discovery to identify the industry-specific schema, then design a custom entity or use Quality Orders (Finance & Operations) or custom fields on the Work Order to preserve incident type, severity, corrective action, and closure status. QHSE data mapping is always a configuration pass because the schema varies by vertical and by customer configuration.

Centerpoint Logistics shipment records map to Dynamics 365 shipment entities or warehouse transfer orders depending on the destination product. Carrier names require normalization if Centerpoint uses a different carrier value set than Dynamics 365's transportation management carrier list. Route assignments migrate as transportation planning records in Finance & Operations or as custom fields on the shipment in Business Central.

Centerpoint record owners (CRM owner, Work Order technician, Employee supervisor) map to Dynamics 365 User records by email match. We extract every distinct owner email referenced across CRM, Work Orders, and HR modules, then cross-reference against the destination User table. Owners without a matching User enter a reconciliation queue for the customer's admin to provision before the relevant phase of migration begins.

Organizations that purchased custom export programs from Red Wing Software may have additional data entities not covered by the standard Data Importer. We review the output format of any custom export programs during discovery, parse the file structure, and map the records to either Dynamics 365 custom objects (Business Central) or extension tables (Finance & Operations) depending on the destination product and the customer's licensing tier. This mapping is always scoped per-customer because custom export programs vary by customer.