Migration Process Sample Clauses

Migration Process. (i) Promptly following confirmation by the Escrow Agent that it has received the Closing Cash Payment, the parties shall commence the transfer and migration of the Purchased Assets, including the Amazon Account, all other Online Marketplace accounts used in connection with the Business and the Intellectual Property Assets, to Buyer (the “Migration Process”). The Migration Process will include, without limitation, the mechanics and other required actions set forth on Exhibit A hereto (the “Migration Mechanics”). (ii) The parties shall use best efforts to transfer the Purchased Assets to Buyer, to carry out all Migration Mechanics and to otherwise complete the Migration Process, as soon as practicable following the Closing Date, but in no event later than four (4) weeks from the Closing Date. (iii) The Migration Process will be deemed “complete” upon the last to occur of the following (the “Completed Migration”): (A) all the Migration Mechanics which are indicated therein as “Escrow Release Conditions” shall have been completed; (B) following completion of such Migration Mechanics, Buyer shall have had an additional period of two (2) days thereafter to fully inspect the Purchased Assets and to ensure that the Business is operating without interruption (the “Inspection Period”); (C) there shall have been no Amazon Seller Restrictions prior to expiration of the Inspection Period; (D) Seller shall have received all necessary Authorization, approvals, consents or waivers to sell, transfer and assign each of the Purchased Assets to Buyer; (E) Seller shall have introduced Buyer to all suppliers, manufacturers, vendors and service providers of the Business; and (F) all Intellectual Property and Intellectual Property Assets shall have been transferred to Buyer. (iv) In the event that Buyer, in its sole discretion, agrees to a deemed Completed Migration despite Seller’s failure to complete any of the Migration Mechanics, such consent shall not be construed as a waiver of the required completion of such Migration Mechanics, and Seller shall be responsible to complete such Migration Mechanics at its sole cost and responsibility, as soon as practicable, following the deemed Complete Migration, but in no event later than thirty (30) days following the date of such deemed Complete Migration. In the event Seller fails to complete any Migration Mechanics within thirty (30) days following the date of such deemed Completed Migration, Buyer shall be entitled, in its sole discr...
Sample 1See All (4)
Migration Process. (a) Subsequent to the Effective Date of this Agreement and Buyer paying the One-Time Payment to Broker, the process to transfer the Assets to the Buyer will begin (“Migration Process”). The Parties understand and agree that the Migration Process typically takes 2 to 8 weeks to complete, but could take substantially longer. The Parties acknowledge and agree that Broker cannot guarantee a specific time-frame to complete the Migration Process; (b) The Migration Process is complete when the Buyer or the Broker, in its sole discretion and in good faith, determines that a sufficient portion of the Assets have been transferred to Buyer such that Buyer can fairly assess the associated revenue during the Inspection Period (“Completed Migration”). It is possible that some portion of the Assets will continue to be transferred to Buyer after the Completed Migration. (c) Broker may cancel any Migration Period and sale if either the Seller or the Buyer has breached a term of this Agreement, including but not limited to representations regarding the Assets’ financial information, performance information, work required to operate the Assets, or other information important to the Asset, as determined in the Broker’s sole and absolute discretion. If Broker determines such a cancellation is required, Broker will cancel the sale, the Asset will be returned to Seller, and the Purchase Price will be returned to Buyer. The Parties agree to cooperate to complete these actions; (d) Either Party’s failure to complete the Migration Process after execution of this Agreement is a material breach of the Agreement; and, (e) The Parties agree to provide Broker all necessary information upon request to facilitate the Migration Process.
Sample 1
Migration Process. After (a) the exchange of executed Closing Deliverables, and (b) the Escrow Agent’s written confirmation of receipt of the Closing Cash, the process to transfer the Acquired Assets to the Buyer will commence (“Migration Process”). The parties agree to work together in good faith and provide their best efforts to transfer the Websites, WP Suite, Software and other Acquired Assets to the Buyer, which process shall include: (i) the provision from the Seller to the Buyer of all codes, passwords and logins necessary for operation of the Business, (ii) transfer of recurring billing for subscriptions of the Business, (iii) transfer of the Seller’s accounts listed on Schedule 1.1, (iv) and transfer of access to the Website’s administration software. The Migration Process will be deemed completed upon the Buyer providing written confirmation to the Seller that the Buyer has, in its discretion, sufficient control of all of the Acquired Assets and no Material Adverse Effect has occurred in connection with the Acquired Assets or the Business during such transfer. Upon completion of the Migration Process, the Escrow Agent shall promptly release the Closing Cash to the Seller.
Sample 1
Migration Process. 3.1 The Parties will undertake the following steps in relation to the ordering, testing and acceptance of a Connection:
Sample 1

Related to Migration Process

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Migration MCK shall provide all requisite assistance as is reasonably requested by NewCo in order to migrate the Services from MCK’s personnel, facilities and environment to NewCo’s (or its designee’s) personnel, facilities and environment, provided, that, other than as expressly set forth in the Service Schedule, NewCo shall be responsible for all third-party costs incurred by MCK and its Affiliates to migrate such Services and, provided further, that, NewCo shall be responsible for all costs associated with operational decisions made by NewCo for its set-up costs and costs to procure items (e.g., selection of Customer Relationship Management software). For the avoidance of doubt, NewCo will be responsible for migration to any new NewCo Data Center, including design, implementation and testing. MCK will provide reasonable support in such efforts. MCK will provide to NewCo an electronic copy in the then-current format of all data that is owned by NewCo (a) a written description of processes and procedures used by MCK in connection with the provision of Services to the Core MTS Business to the extent such descriptions exist, (b) a written description of all system documentation, architecture diagrams and business process diagrams for the systems, processes and controls used in the Core MTS Business to the extent such descriptions exist and (c) written training and onboarding materials used in the Core MTS Business to the extent such materials exist. In addition, MCK will, upon NewCo’s reasonable request, make available knowledgeable MCK personnel for knowledge transfer and discussion at a mutually agreed upon time with respect to the Services and the processes, procedures and systems used in the provision of the Services. The parties will meet in person to establish, within two (2) weeks following the Closing Date, a planning process for the migration of the Services from MCK’s personnel, facilities and environment to NewCo’s (or its designee’s) personnel, facilities and environment. During such meetings, the parties will identify workstreams and workstream leaders, staff project teams for each workstream, identify roles and responsibilities for project team members and create a project charter that will serve collectively as the basis for developing more detailed timelines and specific deliverables for each of the workstreams. At a minimum, there will be a workstream for each functional area that is the subject of Schedules. Each workstream will report to the Project Managers. The parties will meet (in person or by telephone) as often as is reasonably necessary to develop such detailed timelines and specific deliverables for each workstream.

  • Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.

  • Seniority Verification Process i. The new school district shall provide the employee with the necessary verification form at the time the employee achieves continuing contract status. ii. The employee must initiate the seniority verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of receiving a continuing appointment in the new school district. iii. The previous school district(s) shall make every reasonable effort to retrieve and verify the seniority credits which the employee seeks to port.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Sick Leave Verification Process a. The new school district shall provide the employee with the necessary verification form at the time the employee receives confirmation of employment in the school district. b. An employee must initiate the sick leave verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of commencing employment with the new school district. c. The previous school district(s) shall make every reasonable effort to retrieve and verify the sick leave credits which the employee seeks to port.

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Complaints Process The School shall establish and adhere to a process for resolving public complaints which shall include an opportunity for complainants to be heard. The final administrative appeal shall be heard by the School's Governing Board, except where the complaint pertains to a possible violation of any law or term under this Contract. The complaints process shall be readily accessible from the School’s website, as described in Section 11.4.1.