Question 1

What Rocketlane data can Polytomic sync?

Accepted Answer

Projects, tasks, phases, spaces and space documents, time entries and time entry categories, time off, resource allocations, users, and custom field definitions. Two things worth flagging: there is no standalone customers object and no templates object. Customer and company information comes through embedded on projects and users, and template identifiers appear on project and space document records, so the data is available but not as its own table to join against.

Question 2

How does incremental syncing work?

Accepted Answer

Objects that support it filter on updated time, and the checkpoint saved for the next run is the current sync's start time rather than the newest record seen. That is deliberate, since it avoids missing records that change while the sync is still running. Resource allocations work differently: they read across a date range with the start date pushed down to the API, and results are deduplicated by allocation ID rather than checkpointed.

Question 3

How are Rocketlane custom fields handled?

Accepted Answer

Polytomic requests all fields where the API supports it, and custom values arrive as nested arrays on projects, tasks, and users rather than being flattened into individually named columns. The field definitions and their options are available separately as their own object. That means a custom field called Go Live Date does not become its own column automatically; you join the definitions to the values or unpack the nested array in your data warehouse. This design avoids the schema shifting under you every time someone adds a field in Rocketlane.

Question 4

Why do some objects take much longer to sync?

Accepted Answer

Phases, spaces, and space documents are read per project, so Polytomic first enumerates every project and then makes requests for each one's children. A workspace with hundreds of projects therefore generates hundreds of requests for those objects even when little has changed. Combined with Rocketlane's per minute request limit, which Polytomic stays within deliberately, those objects make an ETL run take proportionally longer. If you only need project and task level reporting, leaving the child objects out speeds things up considerably.

Question 5

Why move Rocketlane data into a data warehouse?

Accepted Answer

Because implementation performance only means something next to commercial outcomes. Whether onboarding length predicts churn, whether a segment consistently runs over the hours quoted, and what delivery actually costs against contract value are all joins between Rocketlane, your CRM, and your billing system. Running ETL into your data warehouse makes those questions answerable, and reverse ETL on the same platform can push an at risk flag or projected go live date back onto the CRM record the account team works in.

Rocketlane

Perfect pairings

Incremental project reads

Time and capacity data

Spaces and documents

Example workflows

What you can sync

From Rocketlane

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Rocketlane in minutes

More integrations beyond Rocketlane