REQeV

REQeV Data Migration Terms

Effective date: September 17, 2026

These Data Migration Terms (“Migration Terms”) apply when ECDG, Inc., a California corporation, doing business as REQeV (“REQeV”, “we”, “us” or “our”), helps a customer (“Customer” or “you”) move data into the Services from another system. They form part of the Master Subscription Agreement or other written agreement between REQeV and Customer (the “Agreement”).

Capitalized terms not defined here have the meanings given in the Agreement. If these Migration Terms conflict with an Order Form or a statement of work, the Order Form or statement of work controls.

1. Definitions

“Migration Services” means the data migration services REQeV provides under these Migration Terms, including Standard Migrations and Custom Migrations.

“Source System” means the spreadsheet, file export, applicant tracking system, CRM or other system from which Customer’s data is being migrated.

“Source Data” means the data Customer provides, or authorizes REQeV to retrieve, from a Source System for migration.

“Complete Export” means a full set of Source Data in a supported format, together with any credentials, field mappings and information REQeV reasonably requests to perform the migration.

“Test Pass” means an initial import of all or a representative sample of Source Data into Customer’s REQeV account for Customer’s review.

“Final Pass” means the import of the full Source Data into Customer’s production REQeV account after Customer has reviewed the Test Pass.

2. Standard Migrations

2.1 Supported sources. A “Standard Migration” is a one-time migration from (a) spreadsheet or CSV exports that follow REQeV’s import templates or can be reasonably mapped to them, or (b) an applicant tracking system or CRM that is listed in Customer’s Order Form or in REQeV’s Documentation as a supported source. Migrations from any other source are Custom Migrations.

2.2 What’s included. Subject to the limits of the Source System and its export format, a Standard Migration includes the following data types:

  • candidate records, including contact details, employment and education history, and source information;
  • contacts, such as hiring managers and client contacts;
  • companies, including clients and prospects;
  • jobs and requisitions;
  • pipelines and stages, including each candidate’s current stage for each job;
  • notes;
  • activities, such as logged calls, meetings and tasks, where available in the export;
  • attachments and resumes, subject to the file size and file type limits in the Documentation;
  • custom fields within the scope agreed in the Order Form.

2.3 Field mapping. REQeV will propose a mapping of Source Data fields to REQeV fields. Customer will review and approve the mapping before the Test Pass. Data that does not have a reasonable equivalent in REQeV may be imported into notes or custom fields, or omitted, as agreed with Customer.

2.4 Migration passes. A Standard Migration includes one Test Pass and one Final Pass. Additional passes, or a repeat of a pass because Customer changed its Source Data, mapping or requirements, are subject to the re-migration fees in Section 10.

3. Timeline

3.1 Estimates. REQeV will provide a migration estimate after reviewing the scope and Complete Export. The estimate will cover the Test Pass, Customer’s review period and Final Pass; any committed completion date must be agreed in writing.

3.2 Factors affecting timing. Timelines are estimates, not guarantees. They depend on the volume and quality of Source Data, the size of attachments, how quickly Customer responds to questions and completes its review, the availability of the Source System, and REQeV’s scheduling. REQeV will keep Customer informed of material changes to the expected timeline.

3.3 Delays. If Customer does not provide a Complete Export or complete its review within 30 days after REQeV requests it, REQeV may reschedule the migration based on availability. If Customer does not provide a Complete Export within 90 days after the Order Form start date, REQeV’s obligation to perform an included Standard Migration ends, unless the parties agree otherwise in writing.

4. Custom Migrations

4.1 Scope. A “Custom Migration” is any migration that is not a Standard Migration. Examples include migrations from unsupported or proprietary systems, direct database extracts, API-based extractions, multiple Source Systems, data volumes or attachment sizes above Standard Migration limits, more custom fields than the Standard Migration allows, complex data transformations, or multiple phased cutovers.

4.2 Statement of work. Custom Migrations are quoted separately and performed under a statement of work (“SOW”) or Order Form signed by both parties. The SOW will describe the scope, deliverables, assumptions, timeline, acceptance process and fees. These Migration Terms apply to Custom Migrations except to the extent the SOW states otherwise.

4.3 Scoping. REQeV may ask for a sample export and a scoping call before quoting a Custom Migration. Quotes are valid for 30 days unless stated otherwise.

5. Out of Scope

Unless expressly included in an Order Form or SOW, Migration Services do not include:

  • syncing or importing historical email threads, mailboxes or calendar history;
  • recreating workflows, automations, triggers, sequences or email templates;
  • recreating reports, dashboards or saved searches;
  • recreating user accounts, roles, teams or user permissions;
  • setting up or migrating Third-Party Integrations or job board connections;
  • data cleansing, enrichment, normalization, or deduplication beyond basic matching on email address or other unique identifiers agreed with Customer;
  • migrating data from systems that Customer cannot export from or authorize access to;
  • ongoing or recurring syncing between the Source System and the Services;
  • training beyond the standard onboarding included in Customer’s plan.

REQeV may offer some of these services separately for an additional fee.

6. Customer Responsibilities

6.1 Export and rights. Customer is responsible for obtaining a Complete Export from the Source System, including paying any fees the Source System provider charges. Customer represents that it has all rights, permissions, notices and consents needed to export the Source Data, to provide it to REQeV, and for REQeV to process it in the Services. Customer is responsible for complying with its contract with the Source System provider.

6.2 Credentials. If REQeV needs access to a Source System, Customer will create a dedicated account with the minimum permissions necessary, where the Source System allows it. Customer will share credentials only through a secure method REQeV designates and never by plain email. Customer should change or revoke those credentials after the migration is complete.

6.3 Data freeze or delta. Customer will either stop adding or changing data in the Source System between the Complete Export and the Final Pass, or accept that changes made after the export will not be migrated. If Customer needs changes made after the export to be migrated, REQeV can perform a delta migration for an additional fee, where the Source System supports it.

6.4 Review and validation. Customer will review the results of the Test Pass and the Final Pass and report any issues to REQeV in writing within 10 business days after REQeV notifies Customer that each pass is complete. Customer’s report should describe the issue with enough detail, including examples, for REQeV to investigate it.

6.5 Acceptance. A migration pass is accepted when Customer confirms acceptance in writing, or when 10 business days pass after REQeV’s completion notice without Customer reporting a material issue, whichever happens first. Use of the migrated data in the ordinary course of Customer’s business after the Final Pass also counts as acceptance. REQeV will use reasonable efforts to correct material issues that Customer reports on time and that are caused by REQeV’s migration work.

6.6 Cooperation. Customer will designate a project contact with authority to make decisions about the migration, answer REQeV’s questions promptly, and make knowledgeable personnel available as reasonably needed.

7. Data Security During Migration

7.1 Protection. Source Data is Customer Data under the Agreement and is protected by the Agreement, the Data Processing Addendum and our Security and Privacy at REQeV.

7.2 Transfer. Source Data must be transferred using encrypted methods, such as a secure upload link or encrypted file transfer that REQeV provides. REQeV will not accept Source Data by unencrypted email attachment, and will ask Customer to use a secure method instead.

7.3 Access. Only REQeV personnel and Subprocessors who need access to perform the migration will have access to Source Data and Source System credentials. REQeV will use Source System credentials only for the migration and will not keep them after the migration is complete.

7.4 Deletion of source files. REQeV will delete Source Data files and any working copies created for the migration within 30 days after the Final Pass is accepted, or after the migration is otherwise completed or cancelled. Data imported into Customer’s REQeV account is retained and deleted under the Agreement. Backups are overwritten in the ordinary course as described in the DPA.

7.5 Sensitive data. Customer should remove from Source Data any information it does not need in REQeV, including sensitive personal information such as government identification numbers, health information or background check results. Customer is responsible for any sensitive data it chooses to include.

8. Limitations

8.1 No guarantee of perfect fidelity. Source Systems structure data differently than REQeV. REQeV will use commercially reasonable efforts to migrate Source Data accurately, but does not guarantee that every record, field, format, relationship or timestamp will be transferred exactly as it appears in the Source System.

8.2 Source System limits. The results of a migration depend on what the Source System allows Customer to export. REQeV is not responsible for data that is missing, incomplete, corrupted, truncated or inaccurate in the Source Data, or for limits the Source System places on exports, attachments, API access or rate limits.

8.3 Formatting. Rich text, embedded images, formatting, and file types not supported by REQeV may be converted, simplified or omitted. Historical activity may show the migration date rather than the original date where the Source System does not export original timestamps.

8.4 Source System. REQeV does not modify or delete data in the Source System. Customer is responsible for keeping its own copy of the Source Data until it has confirmed the migration, and for deciding when to close its Source System account.

8.5 Warranty and liability. Migration Services are provided subject to the warranty disclaimers and limitations of liability in the Agreement. Customer’s sole remedy for a defect in Migration Services is for REQeV to use reasonable efforts to correct the defect as described in Section 6.5, or, if REQeV cannot do so, a refund of any separately paid fees for the defective Migration Services.

9. Fees

9.1 Standard Migrations. A Standard Migration is included at no additional charge where Customer’s Order Form says so, and is otherwise charged as stated in the Order Form. An included Standard Migration is available once per customer account and has no cash value if unused.

9.2 Custom Migrations. Custom Migrations are charged as stated in the applicable SOW or Order Form.

9.3 Payment. Unless the Order Form or SOW says otherwise, migration fees are invoiced in advance, are due on the same terms as other fees under the Agreement, and are non-refundable once the Test Pass has started, except as provided in Section 8.5.

9.4 Third-party costs. Customer is responsible for any fees charged by the Source System provider for exports, API access or account extensions.

10. Re-Migration and Additional Work

10.1 Re-migration fees. Additional work is charged at REQeV’s then-current rates, or as stated in the Order Form, where Customer requests:

  • additional Test Passes or Final Passes beyond those included;
  • a repeat of a migration pass because Customer changed its Source Data, field mapping or requirements after approval;
  • a delta migration of data added after the Complete Export;
  • a new migration from a different or additional Source System;
  • a rollback and re-import of data after acceptance.

10.2 No charge for REQeV errors. REQeV will not charge re-migration fees to correct material errors caused by REQeV’s migration work that Customer reports within the review period in Section 6.4.

10.3 Quote first. REQeV will tell Customer the fee for additional work and obtain Customer’s approval before performing it.

11. Changes to These Terms

REQeV may update these Migration Terms from time to time. Changes will not apply to a migration already in progress unless Customer agrees. The version in effect when a migration is ordered applies to that migration.

12. Contact

For questions about a migration or these Migration Terms, contact: