In situations where the deadline is flexible, and requirements are yet to be defined, Agile methodology is recommended for Sales Cloud implementation. Here's why:
* Flexibility and Iterative Approach: Agile methodology accommodates evolving requirements through iterative cycles. This allows the company to start implementing Sales Cloud while refining and defining requirements progressively.
* Quick Start: Agile's incremental approach means the team can begin with basic functionality and enhance it over time, which aligns with the company's goal of getting up and running quickly.
* Salesforce Best Practices: Salesforce recommends Agile methodology for projects with changing requirements and an emphasis on quick delivery, ensuring adaptability and continuous improvement.
* References: Salesforce resources on Agile Project Management advocate for Agile in dynamic environments where flexibility and user feedback are crucial.
In summary, Agile (Option A) is the best methodology for a quick and adaptable Sales Cloud implementation with undefined requirements.

* Using a Roll-up Summary field from the Opportunity to the Account is the best way to meet the requirement of showing the total values of open opportunities on account records when enabling Advanced Currency Management. A Roll-up Summary field is a field that calculates values from related records, such as count, sum, min, max, etc. Advanced Currency Management is a feature that allows users to enable dated exchange rates and track historical exchange rates in Salesforce. By using a Roll-up Summary field from the Opportunity to the Account, Cloud Kicks can display the sum of the open opportunity amounts on each account record, and use the dated exchange rates to convert the currency amounts based on the close date of the opportunities.

To migrate all the sales data into CK's Salesforce instance, the consultant should recommend the following data migration sequence for the objects:
* Accounts
* Opportunities
* Contacts
* Products
* Product Line Items
* Cases
* Leads
* Campaigns
This sequence ensures that all the parent records are created before their child records, and that all the lookup and master-detail relationships are preserved. For example, an opportunity must have an account before it can be created, and a product line item must have an opportunity and a product before it can be created.