Hi Andrea,
1. Answer to First Question (Quotation status between FO and CRM):
Based on implementation experience with combo boxes/drop downs in Dual write the best approach would be to convert the drop down into a string value using custom code in D365 FO and then have the equivalent converted in CRM. As Andre mentioned, you will need to get the mapping right. Either have a Quote In status Sent or won (Enum Values in D365 FO) in CRM which is an easier approach or else have a type conversion in D365 FO where Sent or Won is converted to Active or Won and then send Active or Won values to CRM. Having the equivalent of F&O in CRM would be easier to manage.
2. Answer to Second question (Go-Live for New Company):
Some recommended approaches would be:
1. Create a legal entity in D365 FO and map it with the cdm_company entity in Dataverse.
2. In dual write setup, add the new company to the company filters for relevant mapping. Dual-write follows company contexts so only the new data company will sync.
3. Run intial sync on affected maps. This doesn't need pausing of interfaces etc, only pausing and resuming specific maps if needed for dependencies (if any). Dual write pause and sync in D365 FO should help.
4. Monitor the initial sync details tab for errors, if any.
5. Other recommendations include in case of large data volumes is to migrate data through Data Management export (DMF export) in D365 FO, import to Dataverse using dataflows and enable live sync. This avoids overloading the system and reduces runtime to minutes rather than hours.
6. There is a Dual write async process which is in preview mode that decouples synchronization from live transactions, potentially allowing inital sync on the background without blocking. Its in FO but not Generally available yet. You can try this approach in the test environment or on a test instance for the time being.
References:
Hope this helps. Happy to answer questions, if any.