Plan a measured transition
Connect supported systems or import supported data with an explicit validation and rollback plan. Keep source backups, test a limited scope and reconcile counts before a production cutover. Not every provider, field or workflow can be migrated.
Your domain stays yours
A supported publishing connector can use your existing site. Review permissions, URLs and redirect behavior in staging before connecting production; domain ownership does not guarantee preserved rankings.
Your accounts stay yours
Connection methods differ by provider: OAuth, API credentials or an assisted handoff. Check the supported adapter, plan, scopes and imported data before granting access. Disconnect does not delete data already held by a provider.
Your pipeline stays yours
Keep the current system of record while validating field mappings, identifiers, suppression and duplicate prevention. Test a small scope before changing production workflows; continuity requires your cutover plan.
Supported migration sources, with their rollback status
For data you want inside MarketiQ, these are the importers that exist today — listed from the platform itself, including what each one can and cannot roll back.
Imports run as versioned migration jobs inside your workspace (CRM-manager role): each run records coverage of required and optional columns, invalid rows and a rollback receipt where the importer supports one. Email subscriber imports are double opt-in — nothing is sent to an imported contact without a confirmed consent grant.
“What happens to everything we’ve already built?”
The five concerns we hear most from teams evaluating MarketiQ — and what actually happens to each one when you switch.
“Our organic rankings will reset if we move platforms.”
Inventory your URLs, redirects, sitemap and analytics before publishing. Compare a staging export with the live site. Search engines decide rankings; a connector or content change can affect them and MarketiQ cannot protect a position.
“Years of DA/PA will be lost on a new platform.”
DA and PA are third-party estimates, not assets a migration can guarantee. Preserve source backups, validate canonical URLs and measure observed changes using your chosen provider.
“Onboarding will freeze our roadmap for a quarter.”
Start with a bounded read/draft workflow alongside your current process. Provider approval, data quality, consent review and operational testing determine the timeline; there is no universal completion time.
“Deals in progress will be disrupted mid-cycle.”
Do not stop the source CRM until record counts, identifiers and update direction reconcile. Unsupported objects and automations stay in your source system; validate each supported mapping separately.
“Our sequences and posting cadence will go dark during the switch.”
Your current outreach can continue while MarketiQ observes and drafts. LinkedIn state changes are human-operated: you perform every final Connect, Send, Like, Comment, InMail and profile-save action directly in LinkedIn.
Gradual by design — no cut-over date, no hard switch
MarketiQ runs in parallel with your current process and takes on responsibility only as it proves itself. You control the pace at every step.
01
Connect
Review the supported connection method, scopes and data handling. Back up source data and connect a staging or limited account before production.
02
Learn — read-only
The platform researches your company, market, competitors and channels to build its working context. It reads and analyzes; it does not publish, send or spend.
03
Run in parallel — you approve
Agents draft strategy, content, campaigns and replies alongside your current process. Everything that would touch the outside world ships only with your approval. Your existing motion keeps running underneath.
04
Autonomy — scoped by your approval policy
Autonomy is graduated by risk and owned by you: low-risk internal work can run on its own first, while high-impact actions (live spend, publishing, outbound) stay approval-gated until you widen the policy — and always remain behind guardrails, the exception queue and the kill-switch.
Six rails between you and a bad surprise
Trust isn’t asked for — it’s enforced by the platform’s own governance.
Kill-switch
The workspace kill-switch blocks new guarded actions. Already-dispatched provider operations may finish and require reconciliation; a switch cannot undo an external send.
Approval gates
High-impact internal changes require sign-off. LinkedIn state changes remain human-operated and never auto-run.
Action limits
Daily planning limits and pause controls support deliberate operation; you click every final native LinkedIn control yourself.
Guardrail auto-pause
Experiments and ramp-ups pause themselves automatically when a guardrail metric is breached.
Full audit trail
Inspect recorded actors, operations and receipts. Missing or unknown provider outcomes remain visible and require investigation; an audit entry is not proof of successful execution.
No lock-in
Use supported exports and review retention before disconnecting. API keys, provider grants and downstream copies may need separate revocation or erasure steps.
The questions every team asks before switching
DA and PA are third-party metrics. Track them with the relevant provider and preserve source data; MarketiQ cannot guarantee a score or that new content improves it.
Not necessarily. Supported integrations can coexist with your source systems. Connection methods and supported objects vary. CSV catalogue and subscriber imports have explicit validation and rollback limits; arbitrary provider campaigns and automations are not universally transferable.
Continuity depends on your cutover plan. Keep the existing CRM authoritative, test update direction and deduplication, and reconcile imported identifiers before enabling production writes.
No. Your current tools can keep running while MarketiQ begins in observation and draft mode. LinkedIn state changes are human-operated: MarketiQ prepares the work, and you perform every final action directly in LinkedIn.
Supported catalogue rollback restores pre-import values only when no later edits conflict; newly imported products are archived. Subscriber deletion cannot unsend confirmations or revoke consent. The kill-switch blocks new guarded actions, but unknown or already-dispatched provider operations require reconciliation rather than blind retry.
Provider approval, source quality, volume, consent and staffing determine the timeline. Start with a dry-run and agree on count-reconciliation and recovery checks before a production cutover.
Verify one workflow before expanding
Review the supported sources, run a dry-run, inspect rejected records and reconcile the import. Use the workspace migration console for rollback and portability exports.