Migrate from Furious to Microsoft Dynamics 365 Business Central

Furious Clients migrate 1:1 to Dynamics 365 Accounts. Standard fields (name, email, address, phone, contact info) map directly. We use the company name as the dedupe key. If the agency also uses Dynamics 365 CRM apps, a Contact record is created from the primary Client contact and linked to the Account. Address formats require normalization against Dynamics 365's composite address schema before import.

Furious Projects map to either a Business Central Job or a Finance and Operations Project entity depending on the destination tier. We determine the correct entity during scoping based on project type, billing model, and whether the agency uses Project Operations. Project status (Active, On Hold, Completed) maps to the destination's corresponding status field. Custom project fields map field-by-field to custom fields pre-created in the destination schema. Tasks under the project map to Job Tasks or WBS lines respectively.

Furious Quotes map to Microsoft Dynamics 365 Sales Quote or Sales Order depending on whether the quote is open or has been accepted. Line items migrate with product description, quantity, unit price, and discount. Quote-to-project linkage is preserved by creating the corresponding Job or Project before the Quote import so that the parent reference is satisfied. Custom quote fields map to custom fields on the destination Quote object.

Furious Invoices migrate to Microsoft Dynamics 365 Sales Invoice. We map the client reference, invoice number, line items, amounts, and tax fields. Open invoices are flagged for manual status verification post-migration because any payments processed in Furious between the cutover snapshot and go-live require double-bookkeeping reconciliation. Historical paid invoices migrate with full line detail. Invoice PDFs are flagged for manual re-upload to SharePoint or the document management system.

Furious Purchase Orders map to Dynamics 365 Purchase Orders with vendor reference, PO number, line items, and amounts. Vendor records must be created in Dynamics 365 before PO import so that the vendor lookup is satisfied at insert time. If Furious vendors do not exist as Dynamics 365 Vendors, we create them first during the vendor preparation phase. PO status (Draft, Submitted, Received) maps to the corresponding Purchase Order Status values.

Time entries associate to a user, project, and task in Furious. We resolve the user reference to a Dynamics 365 Worker or User record, the project reference to a Job or Project, and the task reference to a Job Task or WBS Activity. Billable and non-billable flags map to the destination's billable field. Hours and duration values migrate directly. Time entries with no valid project reference are held in a reconciliation queue for admin review before import.

Furious Tasks belong to Projects and have assignees, status, due dates, and optionally hours. We map tasks to the correct Job Task or Project Activity in the destination based on the parent project's entity type. Task custom fields migrate field-by-field to custom fields on the destination task entity. Task status values are mapped to the corresponding Dynamics 365 task status values during transformation.

Furious user records (name, email, role) map to Dynamics 365 Users or Workers depending on whether the destination uses HR integration. We match by email as the primary key. Role strings from Furious do not map directly to Dynamics 365 security roles; we flag each role assignment for manual review post-import and assign the closest Dynamics 365 security role as a default. Inactive users are excluded unless the customer specifies they should be migrated.

Furious custom fields on Projects, Quotes, Invoices, and Tasks require individual field-level mapping during the discovery phase. We discover the full custom field schema, map each field name and type to the nearest Dynamics 365 field type (text, number, date, boolean, option set), pre-create custom fields in the destination schema before data import, and apply them at migration time. Fields with no destination equivalent are flagged for manual post-migration entry.

Furious stores binary file attachments linked to projects, quotes, and invoices. We do not migrate binary file attachments. We flag every record with an attachment and provide a CSV inventory of the records and attachment types for manual re-upload to SharePoint Online, Dataverse, or the Dynamics 365 document management system. Customers should audit attachment volume during discovery to allocate time for re-uploading.

Quote line items migrate as Sales Lines attached to the parent Sales Quote or Sales Order. We resolve the product or service reference, map quantity, unit price, unit of measure, and discount percentage. If the product does not exist in Dynamics 365, we create it as a non-inventory item during the product preparation phase before line item import.

Invoice line items migrate as Sales Invoice Lines attached to the parent Sales Invoice. Product or service descriptions, quantities, unit prices, tax codes, and amounts transfer directly. Line-level discounts map to the discount percent or amount field. Tax codes require mapping to the destination tax group configuration set up in Dynamics 365 before invoice import.