Check your next request against the agreement.
Upload one agreement and paste the last request that made you wince. See what it says in a few minutes.
No card needed · Cancel any time · A$ pricing
Data migrations
Scope control for data migration projects
Migration scope is defined by lists and dates: these objects, from this system, this far back, with this many trial loads, after the client hands over clean data. Every “could you also bring across…” tests one of those edges. Agreeably shows you which one.
Where the boundary moves
The edges clients push on.
-
Objects and history
Contacts and open deals are in; invoices, closed tickets and seven years of activity history usually are not. Requests are matched to the list and to any exclusion that names them.
-
Cleansing and responsibilities
When the client was meant to deduplicate the data and did not, the dependency clause matters. Agreeably treats customer responsibilities as scope items, so a missed one shows up as evidence.
-
Loads and reconciliation
Trial loads, the cut-over window and reconciliation reports are often counted. A fourth trial load is assessed against the three you agreed.
Typical requests
How a few of them might come back.
Illustrative examples. The label always depends on what your own agreement says.
-
“Also migrate three years of invoices, please.”
Potentially additionalThe SOW excludes historical invoices by name.
-
“Can you dedupe the contacts before loading?”
Potentially additionalData cleansing is listed as a client responsibility.
-
“Bring over the contacts’ notes field too.”
UnclearContacts are in scope, but the field mapping appendix referred to is missing.
Write it down
Clauses that make these easy to answer.
The more specific the statement of work, the more requests come back included or potentially additional instead of unclear. Worth having in yours:
Read the guide to SOW clauses →- Source systems and objects, listed
- History depth for each object
- Named exclusions (invoices, attachments, audit history)
- Client data-cleansing responsibilities and dates
- Number of trial loads and the cut-over window
- Reconciliation and sign-off method
FAQ
Data migrations: questions
What if the field mapping is in a separate spreadsheet?
Agreeably analyses the agreement text you provide. If the SOW refers to an appendix you have not uploaded, requests that depend on it come back as unclear and the missing context is named, instead of a guess.
Can it tell that the client missed a dependency?
It treats dependencies and client responsibilities as scope items, so a request to do the client’s part shows the clause that assigned it to them. Whether to charge is still your call.