Jonas Enterprise Service & Construction Software to Dynamics 365 migration
Moving from Jonas Enterprise Service & Construction Software to Dynamics 365 Sales transforms a construction-focused ERP into a Microsoft-native CRM that your sales team already uses through Outlook and Teams. FlitStack AI maps Jonas customer records to Dynamics Accounts, service tickets to Cases, and job-cost data into custom Opportunity fields—preserving original create dates, owner assignments, and job-cost breakdowns so your Dynamics 365 reporting reflects the full project lifecycle from day one.
FlitStack AI migrates accounts, contacts, opportunities, cases and agreement__cs from Jonas Enterprise Service & Construction Software to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2–4 weeks for under 25,000 records with standard Jonas-to-Dynamics field mapping.

What moves from Jonas Enterprise Service & Construction Software to Dynamics 365?
Jonas Enterprise Service & Construction Software stores construction-specific data—job costing, work orders, equipment, service agreements, and payroll tied directly to projects—in a SQL Server-backed ERP that runs on-premise or Jonas Cloud (Azure-hosted).
Read the full summary
Dynamics 365 Sales operates on Microsoft Dataverse with standard CRM entities: Account, Contact, Lead, Opportunity, Case, and Product. There is no native one-to-one entity for Jonas's construction job structure, so FlitStack AI maps Jobs to a combination of Opportunities with custom fields capturing job-cost segments (labor, materials, subcontractor), and Jonas service agreements migrate as custom Agreement__c records linked to Accounts. The migration carries Jonas customers, contacts, equipment records, work orders, service tickets, and active job data into Dynamics 365 Sales. Jonas workflows, service-agreement logic, payroll integrations, and equipment-maintenance schedules do not migrate—they must be rebuilt in Dynamics using Power Automate flows, field-service scheduling, and the built-in Asset management entity. We extract Jonas data via SQL views against the Jonas database (for on-premise) or Jonas API exports (for cloud), validate against the Jonas schema, then load into Dynamics via the Dataverse Web API with parallel processing to handle volume efficiently. Original Jonas record IDs are preserved in Dynamics as Source_System_ID__c for traceability and delta-run deduplication. A delta-pickup window captures any records modified in Jonas during the cutover, typically 24–48 hours, so Dynamics reflects the final state of active projects and open service tickets at go-live. One-click rollback is available if reconciliation fails.
Customer → Account
Jonas 'Customer' is a company-level record storing name, address, billing terms, and credit limits.
How it maps
Maps directly to Dynamics Account via FlitStack AI field mapping. Jonas Customer records containing multiple contacts collapse to a single Account with multiple Contact records linked via the AccountId lookup relationship. When migrating, the Jonas CustomerID is preserved as Source_System_ID__c on the Dynamics Account for traceability and deduplication during subsequent delta runs.
Contact → Contact
Jonas Contact stores individuals linked to a Customer with fields for name, email, phone, role, and the customer they belong to.
How it maps
Maps directly to Dynamics Contact. The Contact.AccountId lookup is resolved from the associated Jonas Customer before migration so foreign-key integrity holds in Dynamics.
Job / Project → Opportunity
Jonas Job is a construction project record with phases, cost codes, WIP tracking, and budget vs. actual labor/materials/subcontractor segments.
How it maps
There is no direct Opportunity equivalent, so FlitStack AI creates a Dynamics Opportunity for each Jonas Job and populates custom fields for Job_Number__c, Contract_Type__c, Budget_Labor__c, Budget_Materials__c, Budget_Subcontractor__c, and WIP__c from the Jonas job-cost breakdown.
Work Order → Case
Jonas Work Order tracks service requests with status, priority, assigned technician, line items for parts, and labor hours.
How it maps
Maps to Dynamics Case with custom fields for Work_Order_Number__c, Technician__c, and Labor_Hours__c. Open work orders migrate as active Cases; completed work orders migrate as resolved Cases with closure dates preserved.
Service Agreement / PMA → Agreement__c (Custom)
Jonas Preventive Maintenance Agreements (PMAs) define recurring service contracts tied to customer equipment with billing frequency and scope of work.
How it maps
Dynamics has no native service-agreement entity, so FlitStack creates an Agreement__c custom table with fields for Agreement_Number__c, Customer__c (lookup to Account), Equipment__c (lookup to Asset), Billing_Frequency__c, and Scope_of_Work__c.
Equipment / Asset → Asset (Field Service)
Jonas Equipment records store make, model, serial number, location, and maintenance history.
How it maps
Maps to Dynamics Asset entity when Dynamics 365 Field Service is licensed. Standalone Dynamics 365 Sales without Field Service requires a custom Asset__c table—your license tier determines the target entity.
- CustomerAccount1:1
- ContactContact1:1
- JobOpportunitytransformed
- Work OrderCasetransformed
- Service AgreementAgreement__ctransformed
- EquipmentAsset1:1
+ 6 more in the mapping below
How Jonas Enterprise Service & Construction Software and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Jonas Enterprise Service & Construction Software | Dynamics 365 |
|---|---|---|
| Data Architecture | Jonas stores all data in a single SQL Server database with normalized tables for Jobs, Customers, WorkOrders, Equipment, Payroll, and Inventory sharing foreign-key relationships across modules. | Dynamics 365 Sales uses Dataverse with modular tables: Account, Contact, Lead, Opportunity, Case, Product—each with its own schema and relationships via lookup fields. |
| CRM vs ERP Scope | Jonas is a full construction ERP combining accounting, job costing, payroll, service management, document control, and CRM in one integrated platform for mechanical and specialty contractors. | Dynamics 365 Sales is a CRM that manages sales processes, customer relationships, and service cases—accounting and job costing require separate Dynamics 365 Finance/Project Operations modules. |
| Record Naming | Jonas uses 'Customer' for companies, 'Contact' for individuals linked to customers, and 'Job' for construction projects with WIP tracking and cost codes. | Dynamics 365 uses Account (not Customer), Contact, and Opportunity for deal pipeline—Jobs require custom fields or Project Service Automation integration. |
| Service Management | Jonas has built-in service dispatch, work order management, preventive maintenance agreements, and field-time capture via eMobile integrated directly with job costing and payroll. | Dynamics 365 Field Service is a separate application handling work order dispatch, scheduling, and service agreements—standard Dynamics 365 Sales only includes basic case management. |
| Integration Ecosystem | Jonas integrates with Procore, QuickBooks Online, and 11 third-party apps (CompanyCam, Fleet Complete, XOi) but has limited API access for custom integrations. | Dynamics 365 Sales connects natively to Microsoft 365, Teams, SharePoint, Power Platform, and 1000+ Power Automate connectors—plus full Dataverse Web API for custom development. |
| Customization Model | Jonas customization is limited to configuration within existing modules; custom fields and objects require Jonas professional services engagement and may be version-dependent. | Dynamics 365 Sales allows unlimited custom tables, columns, and Power Apps extensions on Enterprise licenses—custom fields get a _c suffix and are fully versioned. |
Jonas Enterprise Service & Construction Software to Dynamics 365 field mapping
The 30 most-used fields of 47 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
CustomerNoCustomerAccountNumberAccount -
NameCustomerNameAccount -
Address1CustomerAddress1_StreetAccount -
CityCustomerAddress1_CityAccount -
StateCustomerAddress1_StateOrProvinceAccount
| Jonas Enterprise Service & Construction Software field | Dynamics 365 field | Mapping | Note |
|---|---|---|---|
Customer.CustomerNo | Account.AccountNumber | direct | |
Customer.Name | Account.Name | direct | |
Customer.Address1 | Account.Address1_Street | direct | |
Customer.City | Account.Address1_City | direct | |
Customer.State | Account.Address1_StateOrProvince | direct | |
Customer.ZipCode | Account.Address1_PostalCode | direct | |
Customer.Phone | Account.Telephone1 | direct | |
Customer.Fax | Account.Fax | direct | |
Customer.Email | Account.EmailAddress | direct | |
Customer.BillToName | Account.BillingAddress_Name | direct | |
Customer.TaxID | Account.EIN | direct | |
Customer.CustomerNo | Account.Source_System_ID__c | custom_field_required | Jonas customer number stored for traceability and delta-run deduplication. |
Contact.FirstName | Contact.FirstName | direct | |
Contact.LastName | Contact.LastName | direct | |
Contact.Email | Contact.EmailAddress1 | direct | |
Contact.Phone | Contact.Telephone1 | direct | |
Contact.MobilePhone | Contact.MobilePhone | direct | |
Contact.JobTitle | Contact.JobTitle | direct | |
Contact.Role | Contact.Title | direct | |
Contact.CustomerNo | Contact.AccountId | transformed | Jonas Contact.CustomerNo resolved to Dynamics Account.AccountId before migration. |
Contact.ContactNo | Contact.Source_System_ID__c | custom_field_required | Jonas contact ID stored for traceability. |
Job.JobNo | Opportunity.Job_Number__c | custom_field_required | Jonas job number stored as a custom field on Opportunity. |
Job.Description | Opportunity.Name | direct | |
Job.ContractAmount | Opportunity.EstimatedRevenue | direct | |
Job.ContractType | Opportunity.Contract_Type__c | custom_field_required | Jonas T&M, Lump Sum, or Cost-Plus mapped to custom pick-list. |
Job.LaborBudget | Opportunity.Budget_Labor__c | custom_field_required | Labor budget amount from Jonas job-cost segment. |
Job.MaterialsBudget | Opportunity.Budget_Materials__c | custom_field_required | Materials budget amount from Jonas job-cost segment. |
Job.SubcontractorBudget | Opportunity.Budget_Subcontractor__c | custom_field_required | Subcontractor budget from Jonas job-cost segment. |
Job.WIPAmount | Opportunity.WIP__c | custom_field_required | Work-in-progress amount at migration time preserved as custom currency field. |
Job.Status | Opportunity.StatusCode | value_mapping | Jonas job status (Active, Closed, On Hold) mapped to Opportunity status values. |
What to watch for in a Jonas Enterprise Service & Construction Software to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Jonas Jobs require custom Opportunity fields that Dynamics Sales Professional limits
Dynamics 365 Sales Professional license caps custom tables at 15—Job_Number__c, Contract_Type__c, Budget_Labor__c, Budget_Materials__c, Budget_Subcontractor__c, WIP__c, and Source_System_ID__c alone consume six slots.
How we handle it
Teams with additional custom fields ( Jonas-certified payroll class, union craft codes, Davis-Bacon prevailing wage flags) can exceed this limit on Sales Professional. FlitStack AI audits all custom field requirements during discovery and flags whether your license tier requires a Sales Enterprise upgrade before the migration plan is finalized.
Jonas multi-company setups create duplicate Account records in Dynamics
Jonas supports multi-company/subledger configurations where one legal entity operates as multiple Jonas companies sharing a database but with separate customer and job namespaces.
How we handle it
When these customers map to Dynamics, FlitStack AI must deduplicate by TaxID/EIN—if two Jonas companies share the same customer (e.g., a parent LLC and a subsidiary project company), they collapse to a single Dynamics Account. If the businesses are genuinely separate legal entities with different TaxIDs, they create separate Dynamics Accounts. We surface this mapping decision before migration runs so your team can confirm the collapse rule.
Jonas service agreements need manual rebuild as Dynamics Field Service Agreements
Jonas Preventive Maintenance Agreements (PMAs) define recurring service scopes, billing intervals, and equipment linkages that are deeply integrated with Jonas job costing and payroll.
How we handle it
Dynamics 365 Field Service has an Agreement entity, but it operates on the Field Service scheduling board and Asset lifecycle model—not Jonas's job-cost posting model. FlitStack migrates PMA data as Agreement__c records (custom table) for reference, but the recurring billing logic, service-interval triggers, and technician dispatch rules must be rebuilt in Dynamics Field Service by your admin after migration. We provide a PMA export document listing every agreement's scope, frequency, and linked equipment.
Jonas on-premise SQL exports require a dedicated migration window
Jonas Cloud customers can use Jonas API endpoints for extraction, but Jonas on-premise deployments require FlitStack AI to connect directly to the Jonas SQL Server database with read-only credentials to generate export views.
How we handle it
This requires your Jonas DBA or IT team to grant SELECT access on Jonas tables, expose the database to the FlitStack migration environment (VPN or firewall rule), and coordinate the export timing with your Jonas update schedule. Jonas's SQL schema is not publicly documented—FlitStack reverse-engineers table relationships from the Jonas ERD, which adds 3–5 business days to the discovery phase for on-premise deployments.
Jonas email relay deprecation requires Microsoft 365 SMTP reconfiguration
Jonas email functions currently use Basic Auth against Microsoft Office 365 SMTP relay, which Microsoft is disabling in December 2026.
How we handle it
After migrating to Dynamics 365 Sales, any Jonas-integrated email workflows (J-Mail notifications, Jonas Documents email triggers) will stop working unless reconfigured. FlitStack AI does not migrate Jonas SMTP settings—these must be re-established in Microsoft 365 by your IT team using OAuth 2.0 authentication. We document every Jonas email trigger and notification that relied on SMTP relay so your team can rebuild them as Power Automate cloud flows or Dynamics email templates post-migration.
How the migration runs
Discovery and Jonas schema profiling
FlitStack AI connects to your Jonas database (SQL for on-premise, API for Jonas Cloud) and profiles the schema to identify all active tables: Customers, Contacts, Jobs with cost-code segments, Work Orders with labor lines, Equipment, Inventory, Service Agreements, and Documents.
What this step covers
We generate a Data Profile Report listing record counts per entity, blank field rates, and duplicate candidates. For multi-company Jonas setups, we identify shared customers that will collapse to single Dynamics Accounts. This phase produces the field-mapping specification signed off before any data movement begins.
Design Dynamics custom schema and license check
We audit your Dynamics 365 Sales license tier (Professional vs.
What this step covers
Enterprise) against the custom field count required by the Jonas migration. For every Jonas custom property (contract type, union craft code, WIP segment) that needs a Dynamics custom field, we verify it fits within the license cap. If Sales Professional's 15-table limit is insufficient, we recommend the Enterprise upgrade path before migration. Your Dynamics admin creates the custom Opportunity fields, the Agreement__c table (if Dynamics Field Service is not licensed), and the Source_System_ID__c fields across entities—FlitStack provides the exact schema specification.
Resolve owners and user mapping
Jonas technician assignments on Work Orders and Jonas project managers on Jobs map to Dynamics SystemUsers.
What this step covers
FlitStack AI resolves each Jonas user by email address against your Dynamics 365 tenant—matched users get their records assigned to them; unmatched users are flagged for your admin to create Dynamics accounts or assign to a fallback owner. Jonas employees who are not Dynamics license holders (e.g., field-only staff on Jonas payroll) are not created as Dynamics users but are flagged in the Payroll_Employee_ID__c custom field for post-migration reference.
Run sample migration with field-level diff
A representative slice migrates first—typically 100–500 records spanning Accounts, Contacts, Opportunities (Jobs), Work Orders (Cases), and Equipment.
What this step covers
We generate a field-level diff comparing Jonas source values against Dynamics destination values for every mapped field, including custom Opportunity fields capturing Jonas job-cost segments. You verify that WIP amounts, budget breakdowns, work-order hours, and equipment serial numbers landed correctly before the full run commits. Any field-mapping corrections are applied to the specification and the sample re-runs.
Full migration with delta-pickup and rollback
Full migration loads all Jonas Accounts, Contacts, Opportunities with custom job-cost fields, Cases from Work Orders, custom Agreement__c records, Assets from Equipment, and Products from Inventory into Dynamics 365 Sales.
What this step covers
A delta-pickup window (typically 24–48 hours) captures any Work Orders or Jobs modified in Jonas during the cutover. FlitStack maintains an audit log of every record created or updated in Dynamics with the corresponding Jonas record ID stored in Source_System_ID__c. If reconciliation fails, one-click rollback reverts all Dynamics changes to the pre-migration state.
Post-migration handoff and rebuild reference
FlitStack delivers a Migration Handoff Package containing the complete field-mapping spreadsheet, the Jonas Workflow Export documenting every automation rule and J-Mail trigger, the PMA export listing all service agreements and linked equipment, and the Jonas SQL schema diagram used for the export.
What this step covers
Your Dynamics admin uses this package to rebuild Jonas automations as Power Automate flows, reconfigure SMTP relay with OAuth 2.0 for J-Mail, and activate Dynamics Field Service scheduling if applicable. We schedule a 30-day post-go-live check-in to verify that delta-sync completed cleanly and that no Jonas records were missed during cutover.
Jonas Enterprise Service & Construction Software - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Jonas-to-Dynamics migration pricing reflects record count (especially Jobs with their cost-code breakdowns), the number of active Jonas companies in multi-company setups, custom property count on customer and work-order records, and whether Jonas is deployed on-premise (requiring SQL export) or Jonas Cloud (API-based extraction). Teams with over 50 custom Jonas fields or Jonas service agreements mapping to Dynamics Field Service custom entities fall in the upper price range. Jonas payroll data does not migrate—payroll remains in Jonas or moves to a separate Dynamics 365 Finance instance—and that exclusion keeps scope focused on CRM records. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Jonas Enterprise Service & Construction Software to Dynamics 365 →Why teams move from Jonas Enterprise Service & Construction Software to Dynamics 365
- Jonas users report that the platform's construction-specific features come at the cost of usability—complex housekeeping procedures, overcomplicated setup, and a dated interface make day-to-day CRM tasks harder than they need to be. Dynamics 365 Sales offers a modern, Microsoft-licensed interface that sales and service teams already navigate in Outlook and Teams, reducing training overhead and improving adoption rates for non-field staff.
- Jonas's integrations are limited to a curated list of 11 apps (Procore, QuickBooks Online, CompanyCam, XOi), and the platform lacks a robust public API for custom integrations. Construction firms with custom quoting tools, ERP connections, or third-party scheduling software report that Jonas forces them into workarounds. Dynamics 365 Sales provides full Dataverse Web API access, Power Automate connectors, and the entire Power Platform ecosystem for building custom integrations.
- Jonas charges per-core server licensing plus mandatory modules (Jonas Core User License, SQL Server CALs) that scale poorly as contractors add field crews and office staff. Dynamics 365 Sales pricing is per-user with tiered licenses ($65/user/month for Sales Professional, $105/user/month for Enterprise) that include native Teams integration, Copilot AI, and Power BI reporting—eliminating separate BI licensing costs that Jonas users absorb separately.
- Microsoft is disabling Basic Auth for Office 365 in December 2026, and Jonas email functions rely on SMTP relay configurations that require IT team involvement to switch over. Teams running Jonas on-premise face a forced migration path regardless. Migrating to Dynamics 365 Sales during this window lets firms modernize the CRM layer and resolve the Jonas SMTP dependency simultaneously.
- Jonas serves mechanical contractors and specialty trades with deep job-costing and WIP reporting—but the reporting tools are rigid and tied to Jonas's own report generator. Dynamics 365 Sales pairs with Power BI for unlimited custom reporting, and construction-specific dashboards can be built using the same Microsoft tools that finance and operations teams already use, breaking the data silo that Jonas's integrated-but-closed architecture creates.
Questions, answered
Jonas Enterprise Service & Construction Software to Dynamics 365 migration questions
How long does a Jonas Enterprise to Dynamics 365 Sales migration take?
Most Jonas-to-Dynamics migrations complete in 2–4 weeks of clock time for under 25,000 CRM records. Larger setups with 100,000+ records or Jonas multi-company configurations extend to 6–10 weeks. Jonas on-premise deployments require an additional 3–5 days for SQL schema profiling and DBA coordination before extraction begins. The longest single step is typically the Jonas Job-to-Opportunity field mapping—job-cost segment decomposition into custom Opportunity fields requires your admin to confirm which cost codes map to which custom budget fields before the migration specification is finalized.
Will my Jonas workflows and service-agreement automations migrate to Dynamics 365 Sales?
No. FlitStack AI migrates data and schema only—Jonas workflow rules, J-Mail email triggers, approval chains, automated service-dispatch logic, and Jonas Forms-based approval routing do not transfer. They must be rebuilt in Dynamics using Power Automate flows or Dynamics workflows. Jonas PMAs (Preventive Maintenance Agreements) migrate as reference records in a custom Agreement__c table, but the recurring billing logic and service-interval scheduling must be rebuilt in Dynamics Field Service. We provide a Jonas Workflow Export documenting every automation trigger, condition, and action as a rebuild reference for your Dynamics admin.
What does a Jonas Job become in Dynamics 365 Sales?
Jonas Jobs map to Dynamics Opportunities with custom fields capturing job-cost data. The Jonas Job Number becomes Job_Number__c, the Jonas contract type becomes Contract_Type__c (T&M, Lump Sum, Cost-Plus), and the Jonas cost-code budget segments map to Budget_Labor__c, Budget_Materials__c, and Budget_Subcontractor__c on the Opportunity. Jonas WIP amount migrates to WIP__c for reporting continuity. Jonas Job status (Active, Closed, On Hold) maps to Opportunity StatusCode. There is no native Dynamics Project entity in standard Dynamics 365 Sales—if you need project-scheduling features, Dynamics 365 Project Operations is the appropriate module, but that is a separate licensing and implementation scope.
Can I migrate Jonas service agreements and equipment records to Dynamics 365 Sales?
Yes, but with caveats. Jonas Equipment records migrate to Dynamics Asset entity if you have Dynamics 365 Field Service licensed; otherwise, they require a custom Asset__c table. Jonas Preventive Maintenance Agreements (PMAs) migrate as custom Agreement__c records linked to the Account and Asset, preserving the agreement number, billing frequency, and scope of work. However, the recurring-service scheduling logic, technician dispatch rules, and integration between PMAs and Jonas payroll are not part of the data migration—those require a Dynamics Field Service configuration engagement after the migration is complete.
What happens to Jonas payroll and employee records during the migration?
Jonas payroll data does not migrate to Dynamics 365 Sales—payroll remains in Jonas or moves to a separate Dynamics 365 Finance instance. Jonas Employee records map to Dynamics SystemUser only for users who will have Dynamics CRM licenses. Payroll fields (union status, certified payroll class, direct deposit routing) do not transfer to Dynamics. Unlicensed Jonas employees (field crews, union tradespeople) are not created as Dynamics users but are flagged with Payroll_Employee_ID__c on the corresponding Work Order Case records for post-migration payroll reconciliation in Jonas or Dynamics Finance.
Does the migration affect my Jonas account during the cutover?
No. FlitStack AI uses read-only access on Jonas—whether via SQL SELECT queries (on-premise) or Jonas Cloud API (cloud-hosted). Your team continues working in Jonas during the migration with no downtime. A delta-pickup window (typically 24–48 hours after the full migration run) captures any Work Orders or Jobs modified in Jonas during the cutover so Dynamics reflects the final state of active projects and open service tickets at go-live. We recommend scheduling the delta-pickup window during a low-activity Jonas period to minimize the volume of changes to re-capture.
Will Jonas email functions work after migrating to Dynamics 365 Sales?
Jonas email functions (J-Mail, Jonas Documents email triggers) rely on Basic Auth against Microsoft Office 365 SMTP relay, which Microsoft is disabling in December 2026. After migration, any Jonas-integrated email workflows will stop working unless reconfigured. FlitStack AI does not migrate SMTP settings—these must be re-established in Microsoft 365 by your IT team using OAuth 2.0 authentication. We document every Jonas email trigger and J-Mail notification in the Migration Handoff Package so your team can rebuild them as Power Automate cloud flows or Dynamics email templates. This is a post-migration IT task, not part of the data migration scope.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Bella FSM to Dynamics 365Mapping · history · rollbackSugarcrm to Dynamics 365Mapping · history · rollbackmonday CRM to Dynamics 365Mapping · history · rollbackDrivecentric to Dynamics 365Mapping · history · rollbackCustomer.io to Dynamics 365Mapping · history · rollbackTwenty CRM to Dynamics 365Mapping · history · rollback Jonas Enterprise Service & Construction Software to Odoo CRMMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Jonas Enterprise Service & Construction Software to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote