Agiled Docs

CRM and project integrations help teams bring external work data into Agiled or sync supported records with connected tools.

Providers to Document

Asana, ActiveCollab, Avaza, Bitrix24, ClickUp, Clientjoy, Flowlu, Freedcamp, HubSpot, Jira, Kitchen, Linear, Monday, Moxie, Plutio, ProofHub, Scoro, Service Provider Pro, Tave, Teamleader, Teamwork, Wrike, and Assembly.

Typical Import Objects

Projects
Tasks
Users or assignees
Time entries when supported
CRM contacts, companies, deals, and owners when the provider is CRM-focused

Connection Patterns

Many project apps use OAuth. Some use manual API keys or API secrets. After connecting, open the installed app in Settings > Apps and run Import or Sync if that action is available.

Use the provider account that can see the projects you intend to bring into Agiled, but avoid overly broad access when a narrower workspace or project selection is available.

Before Connecting

Confirm which provider workspace, team, project, or organization should be connected. Many project tools let one user access several workspaces, and connecting the wrong one can import private or irrelevant work.

Ask the provider admin whether Agiled should have read-only import access or sync permissions. Use the smallest access that supports the migration or ongoing workflow.

Choose the Source of Truth

Decide which system owns each object before importing or syncing. For example, Agiled might own billing, client communication, and time tracking while Asana, ClickUp, Jira, or Linear continues to own engineering tasks. If both systems edit the same task fields, agree on the direction of updates before enabling a repeat sync.

For one-time migrations, import a small project first and verify the project name, task titles, assignees, due dates, statuses, and time entries before bringing over the rest of the workspace. Keep the original export or provider workspace available until the Agiled records have been reviewed.

After Importing

Review imported projects from Productivity > Projects. Open a few records and confirm that tasks, assignees, dates, and related clients still make sense inside Agiled. Clean up duplicate projects before assigning work, starting timers, or building reports from the imported data.

If the provider supports repeat sync, check the first sync run after making a change in the provider and again after making a change in Agiled. This confirms which side updates which fields and prevents teams from relying on a sync that does not cover the field they care about.

Field Mapping Checks

Spot-check these fields after the first import:

project name and status
task title and description
assignee and creator
due dates and priorities
comments or notes when supported
time entries when supported
client or account links

If the provider has custom statuses, map them to Agiled statuses before using the imported projects for reporting.

Migration Review Checklist

Before inviting the team to work from imported projects:

compare counts with the provider
review one project from each imported workspace or team
check task owners and due dates
clean duplicate or archived projects
decide which system owns future edits
test one sync after a safe provider-side change

CRM and Project App Integrations