Getting started

How objects are counted

DatMig measures migrations by the object count: one migrated item is one object. Understanding what counts helps you estimate a migration and stay within your plan.

What counts as an object

Any distinct item that either has to be queried seperately from the source platform or has to be written seperately in the target platform, is counted as one object. Examples are a project, a task, a subtask, a comment, an attachment, a custom-field value, a time entry, a dependency, etc. A task with 3 comments and 2 attachments is 6 objects: the task plus each of its pieces.

Different platform APIs have different ways of exposing the respective platform's data model, so object counts are fully dependent on how the API supports querying different items. Simply put, any item appearing in the migration job list with the Migrated status is counted as an object. Failed objects are not counted against your migration limit.

Your monthly limit

• Each plan includes a monthly object allowance: Free 500, Pro 3,000, Business 7,000, and a custom amount for Enterprise.
• Every migration reports its object count live, so you always know where you stand.
• If a migration hits your limit, it pauses automatically; no data is lost, and you can resume the migration from where it left off after a subscription upgrade or after the limit reset based on your subscription renewal. You can check Settings > Subscription to find your next renewal date.

Because counting is per object, a small test migration costs only a handful of objects, letting you preview the result before committing to a full fledged migration.