• Replies 13 replies
  • Subscribers 2 subscribers
  • Views 19 views
  • Users 0 members are here
Options
Related

Anyone using FieldPulse alongside another system? How do you manage the overlap?

Devon Marsh

We're in that awkward middle ground where FieldPulse handles most of our field operations, but we still have a legacy CRM that sales refuses to give up (and honestly, it's got 10 years of customer history that would be painful to migrate). Right now we're doing a lot of manual CSV exports and it's... not great.

Curious how others are handling this. Are you:

  • Running dual systems with some kind of sync?
  • Using FieldPulse as the source of truth for some data and the other system for others?
  • Just living with the redundancy?

YMMV obviously, but I'd love to hear what's actually working in practice vs. what sounds good in theory. Any gotchas worth sharing?

Parents

  • We're running FieldPulse + a custom-built scheduling tool from 2019 that our previous IT team built. It's terrible and I want to kill it, but we have three major clients whose service agreements are built around data exports from that system.

    Current approach: FieldPulse is source of truth for daily operations. Legacy system gets a weekly CSV dump for those three clients. It's stupid, it adds 2 hours of work every Friday, and my team can't move forward on consolidating until those contracts renew next year.

    Sometimes the overlap isn't technical, it's contractual. Plan for that.

Reply

  • We're running FieldPulse + a custom-built scheduling tool from 2019 that our previous IT team built. It's terrible and I want to kill it, but we have three major clients whose service agreements are built around data exports from that system.

    Current approach: FieldPulse is source of truth for daily operations. Legacy system gets a weekly CSV dump for those three clients. It's stupid, it adds 2 hours of work every Friday, and my team can't move forward on consolidating until those contracts renew next year.

    Sometimes the overlap isn't technical, it's contractual. Plan for that.

Children
No Data