CRM migration
Field-level mapping, validation, and rollback between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Jonas Enterprise Service & Construction Software
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
12 of 12
objects map 1:1 between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
2–4 weeks
Overview
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). 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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Jonas Enterprise Service & Construction Software platform overview
Scorecard, SWOT, gotchas, and pricing for Jonas Enterprise Service & Construction Software.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Jonas Enterprise Service & Construction Software object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Jonas Enterprise Service & Construction Software
Customer
Microsoft Dynamics 365 Sales
Account
1:1Jonas 'Customer' is a company-level record storing name, address, billing terms, and credit limits. 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.
Jonas Enterprise Service & Construction Software
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Jonas Contact stores individuals linked to a Customer with fields for name, email, phone, role, and the customer they belong to. 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.
Jonas Enterprise Service & Construction Software
Job / Project
Microsoft Dynamics 365 Sales
Opportunity
1:1Jonas Job is a construction project record with phases, cost codes, WIP tracking, and budget vs. actual labor/materials/subcontractor segments. 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.
Jonas Enterprise Service & Construction Software
Work Order
Microsoft Dynamics 365 Sales
Case
1:1Jonas Work Order tracks service requests with status, priority, assigned technician, line items for parts, and labor hours. 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.
Jonas Enterprise Service & Construction Software
Service Agreement / PMA
Microsoft Dynamics 365 Sales
Agreement__c (Custom)
1:1Jonas Preventive Maintenance Agreements (PMAs) define recurring service contracts tied to customer equipment with billing frequency and scope of work. 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.
Jonas Enterprise Service & Construction Software
Equipment / Asset
Microsoft Dynamics 365 Sales
Asset (Field Service)
1:1Jonas Equipment records store make, model, serial number, location, and maintenance history. 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.
Jonas Enterprise Service & Construction Software
Inventory / Parts
Microsoft Dynamics 365 Sales
Product
1:1Jonas Inventory tracks parts and materials with part numbers, descriptions, unit costs, and warehouse locations. Maps to Dynamics Product with Name, Product Number (Jonas part number), and Standard Cost (Jonas unit cost). Jonas inventory warehouses do not map to Dynamics—warehouse tracking requires a separate inventory management solution or Dynamics 365 Supply Chain Management.
Jonas Enterprise Service & Construction Software
Quote / Proposal
Microsoft Dynamics 365 Sales
Quote / Opportunity Product
1:1Jonas Quote records store quoted amounts with line items for labor and materials tied to specific jobs. Migrates to Dynamics Quote entities linked to the corresponding Opportunity (mapped from the Jonas Job). Quote line items map to Opportunity Product records with Unit Price from the Jonas quote amount and Quantity representing the estimated unit count.
Jonas Enterprise Service & Construction Software
Employee
Microsoft Dynamics 365 Sales
SystemUser
1:1Jonas Employee records contain payroll data, certifications, union status, and field-time assignments. Payroll does not migrate to Dynamics 365 Sales—Employee records map to Dynamics SystemUser only for users who will have Dynamics licenses, with Payroll_Employee_ID__c stored as a custom field for reference. Unlicensed employees are not created as Dynamics users.
Jonas Enterprise Service & Construction Software
Document
Microsoft Dynamics 365 Sales
SharePoint / Note
1:1Jonas Documents stores project files, drawings, and client communications linked to Jobs, Customers, or Work Orders. Files migrate to SharePoint Document Libraries connected to the corresponding Dynamics Account or Opportunity. Jonas document metadata (document type, created date, author) is preserved as Note records in Dynamics pointing to the SharePoint file location.
Jonas Enterprise Service & Construction Software
Payroll / Time Entry
Microsoft Dynamics 365 Sales
None
1:1Jonas payroll, direct deposit configurations, union payroll rules, certified payroll, and time-entry uploads do not migrate. Time-entry data for active Jobs is not a standard Dynamics 365 Sales object—payroll remains in Jonas or moves to a separate Dynamics 365 Finance instance. We flag which Jonas employees have Dynamics user licenses so Jonas payroll can be reconciled against the corresponding SystemUser records post-migration.
Jonas Enterprise Service & Construction Software
Workflow / Automation
Microsoft Dynamics 365 Sales
Power Automate / Power Apps
1:1Jonas workflow rules, email triggers, approval chains, and automated service-dispatch logic are platform-specific and do not export. FlitStack AI provides a Jonas Workflow Export documenting each rule's trigger, condition, and action so your Dynamics admin can rebuild equivalent Power Automate flows. Jonas's J-Mail email integration requires SMTP relay reconfiguration in Microsoft 365.
| Jonas Enterprise Service & Construction Software | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Customer | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Job / Project | Opportunity1:1 | Fully supported | |
| Work Order | Case1:1 | Fully supported | |
| Service Agreement / PMA | Agreement__c (Custom)1:1 | Fully supported | |
| Equipment / Asset | Asset (Field Service)1:1 | Fully supported | |
| Inventory / Parts | Product1:1 | Fully supported | |
| Quote / Proposal | Quote / Opportunity Product1:1 | Fully supported | |
| Employee | SystemUser1:1 | Fully supported | |
| Document | SharePoint / Note1:1 | Fully supported | |
| Payroll / Time Entry | None1:1 | Fully supported | |
| Workflow / Automation | Power Automate / Power Apps1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Jonas Enterprise Service & Construction Software gotchas
No public REST/Bulk API for data export
Payroll-to-job-cost link must be explicitly mapped
Multi-company structures fragment customer and vendor IDs
Documents reference network file paths or database BLOBs
Jonas Forms cannot be migrated to non-Jonas systems
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
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. 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. 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. 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. 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. 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. 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.
Platform deep dives
Jonas Enterprise Service & Construction Software
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Jonas Enterprise Service & Construction Software: Not publicly documented.
Data volume sensitivity
Jonas Enterprise Service & Construction Software doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Jonas Enterprise Service & Construction Software
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.