Data Migration Policy
Effective from : January 2025
PLEASE READ THESE DATA MIGRATION TERMS AND CONDITIONS (“TERMS”) CAREFULLY BEFORE UTILIZING ANY DATA MIGRATION SERVICES PROVIDED BY ZUPER INC. (“ZUPER”).
By executing an Order Form, Statement of Work, or Zuper’s Standard Terms that reference or incorporate these Terms, the Customer agrees to be bound by and comply with these Data Migration Terms, which form an integral part of the overall agreement between Zuper and the Customer (collectively, the “Agreement”).
If you are entering into the Agreement on behalf of an entity, you represent and warrant that you are authorized to bind such entity. Any conflicting or additional terms proposed by Customer are expressly rejected. Acceptance is limited to these Terms.
DATA MIGRATION TERMS AND CONDITIONS
These Data Migration Terms and Conditions (“Data Migration Terms”) govern the scope, responsibilities, and limitations of the data migration services (“Data Migration”) to be provided by Zuper Inc. (“Zuper”) to the customer (“Customer”) under the applicable service order or agreement (“Agreement”).
1. General Scope and Limitations
1.1. No Data Management or Manipulation
Zuper shall not be responsible for managing, cleansing, deduplicating, or transforming Customer Data. Customer is solely responsible for ensuring that data is complete, accurate, and properly formatted in accordance with Zuper’s migration requirements.
1.2. Unique Record Identifier Requirement
Each record submitted by Customer must contain a single unique record ID or identifier. Zuper does not support multi-field uniqueness checks (e.g., combinations such as first name + email + phone).
1.3. Migration Template Format
Zuper shall provide data migration templates in CSV format for download by Customer. Customer shall populate and return the templates in CSV format only. No other file formats (e.g., .sql, .doc, .xlsx, .jpg, .pdf) shall be accepted.
1.4. Unstructured Data Exclusion
Zuper shall not migrate unstructured data, including but not limited to images, videos, attachments, or long-form text fields such as notes. Zuper shall not parse or interpret unstructured data for conversion into structured formats.
1.5. Geo-Coordinates and Credit Card Data
Zuper will not convert physical addresses to geo-coordinates, nor will it receive, process, or store credit card information under any circumstances.
2. Included Out-of-the-Box Data Migration (No Additional Cost)
2.1. Eligible Modules for Self-Serve Import
Zuper supports out-of-the-box CSV import by Customer for the following modules:
2.2. Row Limit
Maximum of 25,000 rows per module. If row count exceeds the limit, data must be split across multiple files by Customer.
2.3. Reference
Customer shall refer to Zuper’s official documentation available at:
https://care.zuper.co/portal/en/kb/articles/data-import#TransactionData_Modules
3. Data Migration Requiring Additional Scope (Fee-Based)
3.1. General Requirements
Where Zuper is engaged to perform Data Migration services beyond the out-of-the-box offering, the following limitations apply:
3.2. Number of Data Sets
Zuper will migrate up to five (5) primary data sets (e.g., Contacts, Jobs, Quotes, Proposals, Parts/Assets). Any request to migrate additional data sets is subject to Zuper’s approval and may incur additional fees.
3.3. Scope of Data
Zuper will migrate one (1) primary data table containing active/current data not older than two (2) years from the Agreement’s effective date and up to four (4) related/associated data tables, provided Customer supplies the necessary data mapping.
Example: Active Contacts (Primary) with associated Jobs, Quotes, Proposals, and Service Tasks (Related).
4. Data Mapping and Timestamps
4.1. System Timestamps
Zuper cannot backdate system-generated timestamps during migration. Such fields (e.g., created date, status update time) will reflect the date of import, not the original historical value.
4.2. Transactional Data Dependencies
When importing transactional data (e.g., Jobs), all mandatory fields from associated modules (e.g., Customer Email for Customers) must be present to allow proper linkage and data integrity.
5. Data Migration Plan and Delays
5.1. Sign-Off Requirement
Data migration shall not commence until Customer has reviewed and signed off on the Data Migration Plan provided by Zuper. Any changes to the plan at Customer’s request shall require a change order and may result in additional fees.
5.2. Delays and Pausing
If the project is delayed due to Customer’s failure to provide required data or complete migration tasks, Zuper reserves the right to pause the implementation. Project pauses may result in reassignment of Zuper personnel, ramp-up delays, and additional charges. Customer acknowledges that delays may impact project timelines.
6. Customer Responsibilities
6.1. Assigned Resource Commitment
Customer shall allocate and maintain at least one (1) assigned resource to support Data Migration activities for no less than 10–15 hours per week. The assigned resource must:
7. Miscellaneous
7.1. Long Text and Notes
Zuper does not support parsing or transforming long-text fields (e.g., “Notes”) into structured data formats (e.g., recurring jobs).
7.2. Entire Agreement
These Data Migration Terms are incorporated into and form a part of the Agreement. In the event of any conflict between these terms and the Agreement, these terms shall govern as to data migration matters.
By executing an Order Form, Statement of Work, or Zuper’s Standard Terms that reference or incorporate these Terms, the Customer agrees to be bound by and comply with these Data Migration Terms, which form an integral part of the overall agreement between Zuper and the Customer (collectively, the “Agreement”).
If you are entering into the Agreement on behalf of an entity, you represent and warrant that you are authorized to bind such entity. Any conflicting or additional terms proposed by Customer are expressly rejected. Acceptance is limited to these Terms.
DATA MIGRATION TERMS AND CONDITIONS
These Data Migration Terms and Conditions (“Data Migration Terms”) govern the scope, responsibilities, and limitations of the data migration services (“Data Migration”) to be provided by Zuper Inc. (“Zuper”) to the customer (“Customer”) under the applicable service order or agreement (“Agreement”).
1. General Scope and Limitations
1.1. No Data Management or Manipulation
Zuper shall not be responsible for managing, cleansing, deduplicating, or transforming Customer Data. Customer is solely responsible for ensuring that data is complete, accurate, and properly formatted in accordance with Zuper’s migration requirements.
1.2. Unique Record Identifier Requirement
Each record submitted by Customer must contain a single unique record ID or identifier. Zuper does not support multi-field uniqueness checks (e.g., combinations such as first name + email + phone).
1.3. Migration Template Format
Zuper shall provide data migration templates in CSV format for download by Customer. Customer shall populate and return the templates in CSV format only. No other file formats (e.g., .sql, .doc, .xlsx, .jpg, .pdf) shall be accepted.
1.4. Unstructured Data Exclusion
Zuper shall not migrate unstructured data, including but not limited to images, videos, attachments, or long-form text fields such as notes. Zuper shall not parse or interpret unstructured data for conversion into structured formats.
1.5. Geo-Coordinates and Credit Card Data
Zuper will not convert physical addresses to geo-coordinates, nor will it receive, process, or store credit card information under any circumstances.
2. Included Out-of-the-Box Data Migration (No Additional Cost)
2.1. Eligible Modules for Self-Serve Import
Zuper supports out-of-the-box CSV import by Customer for the following modules:
- Organization
- Customer
- Properties
- Jobs (Import of Customer or Organization is mandatory)
- Products, Parts & Services
- Assets
- Users
2.2. Row Limit
Maximum of 25,000 rows per module. If row count exceeds the limit, data must be split across multiple files by Customer.
2.3. Reference
Customer shall refer to Zuper’s official documentation available at:
https://care.zuper.co/portal/en/kb/articles/data-import#TransactionData_Modules
3. Data Migration Requiring Additional Scope (Fee-Based)
3.1. General Requirements
Where Zuper is engaged to perform Data Migration services beyond the out-of-the-box offering, the following limitations apply:
- File Size Limit: 25 MB per file
- Row Limit: 30,000 rows per module/entity
- Format: Single sheet only (no sub-sheets)
- Each record must have a single unique ID (no multi-column uniqueness)
3.2. Number of Data Sets
Zuper will migrate up to five (5) primary data sets (e.g., Contacts, Jobs, Quotes, Proposals, Parts/Assets). Any request to migrate additional data sets is subject to Zuper’s approval and may incur additional fees.
3.3. Scope of Data
Zuper will migrate one (1) primary data table containing active/current data not older than two (2) years from the Agreement’s effective date and up to four (4) related/associated data tables, provided Customer supplies the necessary data mapping.
Example: Active Contacts (Primary) with associated Jobs, Quotes, Proposals, and Service Tasks (Related).
4. Data Mapping and Timestamps
4.1. System Timestamps
Zuper cannot backdate system-generated timestamps during migration. Such fields (e.g., created date, status update time) will reflect the date of import, not the original historical value.
4.2. Transactional Data Dependencies
When importing transactional data (e.g., Jobs), all mandatory fields from associated modules (e.g., Customer Email for Customers) must be present to allow proper linkage and data integrity.
5. Data Migration Plan and Delays
5.1. Sign-Off Requirement
Data migration shall not commence until Customer has reviewed and signed off on the Data Migration Plan provided by Zuper. Any changes to the plan at Customer’s request shall require a change order and may result in additional fees.
5.2. Delays and Pausing
If the project is delayed due to Customer’s failure to provide required data or complete migration tasks, Zuper reserves the right to pause the implementation. Project pauses may result in reassignment of Zuper personnel, ramp-up delays, and additional charges. Customer acknowledges that delays may impact project timelines.
6. Customer Responsibilities
6.1. Assigned Resource Commitment
Customer shall allocate and maintain at least one (1) assigned resource to support Data Migration activities for no less than 10–15 hours per week. The assigned resource must:
- Possess working knowledge of the source system(s)
- Provide accurate data mappings from source to Zuper
- Validate migrated data
- Review and sign off on the migration plan
7. Miscellaneous
7.1. Long Text and Notes
Zuper does not support parsing or transforming long-text fields (e.g., “Notes”) into structured data formats (e.g., recurring jobs).
7.2. Entire Agreement
These Data Migration Terms are incorporated into and form a part of the Agreement. In the event of any conflict between these terms and the Agreement, these terms shall govern as to data migration matters.
